MsQuic: Improper Certificate Validation in Microsoft.Native.Quic.MsQuic.OpenSSL
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.4.20, 2.5.11, 2.6.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- microsoft msquic
fixed in 2.4.20; From 2.5.0 · fixed in 2.5.11; From 2.6.0 · fixed in 2.6.1
- Microsoft.Native.Quic.MsQuic.OpenSSLNuGet
fixed in 2.4.20
- Microsoft.Native.Quic.MsQuic.OpenSSLNuGet
From 2.5.0 · fixed in 2.5.11
- Microsoft.Native.Quic.MsQuic.OpenSSLNuGet
From 2.6.0 · fixed in 2.6.1