Service abort via unbounded QUIC response queue
Published Dec 12, 2023 · Updated Aug 2, 2024
State exhaustion in h2o 2.3.0-beta2 and earlier allows remote attackers to abort HTTP/3 service through crafted QUIC traffic. In deps/quicly/lib/quicly.c, each received PATH_CHALLENGE schedules a separately heap-allocated PATH_RESPONSE node without bounding the pending queue, so retained connection state grows with repeated frames. The attack requires HTTP/3 to be enabled; HTTP/1 and HTTP/2 do not use QUIC and are unaffected, and exhaustion ends in a process abort rather than data disclosure or modification.
Summary
What happened
State exhaustion in h2o 2.3.0-beta2 and earlier allows remote attackers to abort HTTP/3 service through crafted QUIC traffic. In deps/quicly/lib/quicly.c, each received PATH_CHALLENGE schedules a separately heap-allocated PATH_RESPONSE node without bounding the pending queue, so retained connection state grows with repeated frames. The attack requires HTTP/3 to be enabled; HTTP/1 and HTTP/2 do not use QUIC and are unaffected, and exhaustion ends in a process abort rather than data disclosure or modification.
The record
- CVE
- CVE-2023-50247
- Published
- Dec 12, 2023
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-770, T1499.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 12, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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