CVE-2024-22189: QUIC's Connection ID Mechanism vulnerable to Memory Exhaustion Attack
An attacker can cause its peer to run out of memory by sending a large number of NEWCONNECTIONID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRECONNECTIONID frame.
Published Apr 2, 2024 · Updated Apr 5, 2024
Affected packages
github.com/quic-go/quic-go
- Ecosystem
- Go
- Affected
- < 0.42.0
- Fixed in
- 0.42.0
- Check
go list -m github.com/quic-go/quic-go
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
An attacker can cause its peer to run out of memory by 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.
I published a more detailed description of the attack and its mitigation in this blog post: https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-management/. I also presented this attack in the IETF QUIC working group session at IETF 119: https://youtu.be/JqXtYcZAtIA?si=nJ31QKLBSTRXY35U&t=3683
There's no way to mitigate this attack, please update quic-go to a version that contains the fix.
Credited to marten-seemann.
References
- https://github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c478
- https://github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac45147c85ed47a
- https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-management
- https://www.youtube.com/watch?v=JqXtYcZAtIA&t=3683s
- https://nvd.nist.gov/vuln/detail/CVE-2024-22189
- https://github.com/advisories/GHSA-c33x-xqrf-c478
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-40898
quic-go: HTTP/3 QPACK Trailer Expansion Memory Exhaustion
medium5.3Jun 3, 2026CVE-2025-64702
quic-go HTTP/3 QPACK Header Expansion DoS
medium5.3Dec 11, 2025CVE-2025-59530
quic-go: Panic occurs when queuing undecryptable packets after handshake completion
high7.5Oct 10, 2025CVE-2025-29785
quic-go Has Panic in Path Probe Loss Recovery Handling
high7.5Jun 3, 2025CVE-2024-53259
quic-go affected by an ICMP Packet Too Large Injection Attack on Linux
medium6.5Dec 2, 2024CVE-2023-49295
quic-go's path validation mechanism can be exploited to cause denial of service
medium6.4Jan 10, 2024
