GHSA-2x7m-gf85-3745 json
Remote Denial of Service Vulnerability in Microsoft QUIC
published 2y ago modified last yr.
- cvss
- 7.5
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
### Impact The MsQuic server will continue to leak memory until no more is available, resulting in a denial of service.
### Patches The following patch was made:
- Fix Memory Leak from Multiple Decodes of TP - https://github.com/microsoft/msquic/commit/5d070d661c45979946615289e92bb6b822efe9e9
### Workarounds Beyond upgrading to the patched versions, there is no other workaround.
### MSRC CVE Info https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-26190
Patch / fix
- nuget Microsoft.Native.Quic.MsQuic.OpenSSL 2.1.12, 2.2.7, 2.3.5
- nuget Microsoft.Native.Quic.MsQuic.Schannel 2.1.12, 2.2.7, 2.3.5
Is GHSA-2x7m-gf85-3745 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| nuget | Microsoft.Native.Quic.MsQuic.OpenSSL | <2.1.12 >=2.2.0, <2.2.7 >=2.3.0, <2.3.5 |
2.1.12 2.2.7 2.3.5 |
| nuget | Microsoft.Native.Quic.MsQuic.Schannel | >=2.2.0, <2.2.7 >=2.3.0, <2.3.5 <2.1.12 |
2.2.7 2.3.5 2.1.12 |
Classification
- Weakness
-
- CWE-401 Missing Release of Memory after Effective Lifetime
References
-
github.com
/microsoft/msquic/commit/5d070d661c45979946615289e92bb6b822efe9e9
web
-
github.com
/microsoft/msquic/commit/933f7b79949bc588945672396d70b661143bb8f0
web
-
github.com
/microsoft/msquic/security/advisories/GHSA-2x7m-gf85-3745
web
-
github.com
/microsoft/msquic
package
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2024-26190
web
Sources
- GitHub Advisory GHSA-2x7m-gf85-3745
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.