Remote memory exhaustion via unbounded control-frame queue
Published Apr 4, 2024 · Updated Aug 23, 2024
Resource exhaustion in quic-go before 0.42.0 allows remote attackers to exhaust peer memory through crafted QUIC frames. The connection-ID handler queues a RETIRE_CONNECTION_ID response for each attacker-supplied NEW_CONNECTION_ID retirement without bounding the control-frame queue. A peer must sustain a QUIC connection, selectively acknowledge packets, and manipulate RTT estimates to suppress responses until memory is exhausted.
Summary
What happened
Resource exhaustion in quic-go before 0.42.0 allows remote attackers to exhaust peer memory through crafted QUIC frames. The connection-ID handler queues a RETIRE_CONNECTION_ID response for each attacker-supplied NEW_CONNECTION_ID retirement without bounding the control-frame queue. A peer must sustain a QUIC connection, selectively acknowledge packets, and manipulate RTT estimates to suppress responses until memory is exhausted.
The record
- CVE
- CVE-2024-22189
- Published
- Apr 4, 2024
- Updated
- Aug 23, 2024
- Vendor
- quic-go
- Product
- quic-go
- Classifications
- CWE-770, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 4, 2024CVE publishedPublication date reported by the CVE source.
- Aug 23, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.42.0
- Affected versionversion=< 0.42.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo