CVE-2024-22189: QUIC's Connection ID Mechanism vulnerable to Memory Exhaustion Attack
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.
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.
References
- github.com/advisories/GHSA-c33x-xqrf-c478
- github.com/quic-go/quic-go
- github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac45147c85ed47a
- github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c478
- nvd.nist.gov/vuln/detail/CVE-2024-22189
- seemann.io/posts/2024-03-19-exploiting-quics-connection-id-management
- www.youtube.com/watch?v=JqXtYcZAtIA&t=3683s
Detect and mitigate CVE-2024-22189 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →