MsQuic: Improper Certificate Validation in Microsoft.Native.Quic.MsQuic.OpenSSL
microsoft msquic
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft.Native.Quic.MsQuic.OpenSSL NuGet |
|
|
microsoft msquic
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft.Native.Quic.MsQuic.OpenSSL NuGet |
|
|
MsQuic is a cross-platform C implementation of the IETF QUIC protocol exposed to C, C++, C#, and Rust. Prior to 2.4.20, 2.5.11, and 2.6.1, MsQuic clients using the OpenSSL or QuicTLS TLS backend do not properly verify that a server certificate matches the intended target server hostname. An on-path attacker can therefore present a certificate that does not match the intended target hostname and spoof the server in a man-in-the-middle attack. The Schannel backend is not affected. This issue is fixed in versions 2.4.20, 2.5.11, and 2.6.1.
From the CVE record · GitHub_M
MsQuic clients using the OpenSSL or QuicTLS backend do not properly check that a server certificate matches the intended hostname. An on-path attacker can present a certificate for a different hostname and spoof the server in a man-in-the-middle attack. The Schannel backend is not affected.
Check deployments of MsQuic clients using OpenSSL or QuicTLS, including NuGet Microsoft.Native.Quic.MsQuic.OpenSSL versions below 2.4.20, from 2.5.0 through 2.5.10, or from 2.6.0 up to but not including 2.6.1.