CVE-2024-22189: QUIC's Connection ID Mechanism vulnerable to Memory Exhaustion Attack
Affected: quic-go · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 66% of scored CVEs
DescriptionCVE.org
quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a `RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- quic-go · quic-go< 0.42.0
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- quic-go
- Published
- April 2024
CoverageNo articles yet
No CyberSIXT article names CVE-2024-22189 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-770cwe.mitre.org
- github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c4github.com
- github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac451github.com
- seemann.io/posts/2024-03-19-exploiting-quics-connection-id-managseemann.io
- youtube.com/watch?v=JqXtYcZAtIA&t=3683syoutube.com