Service interruption via unbounded HTTP/2 flow control
Published Aug 31, 2022 · Updated Aug 2, 2024
Uncontrolled resource consumption in Red Hat Undertow allows remote attackers to interrupt HTTP/2 service through flow-control handling. The HTTP/2 receive-flow-control path inadequately limits client-driven activity because the earlier correction for the same condition was incomplete. An unauthenticated network client must reach an HTTP/2-enabled listener; the documented impact is server overhead or denial of service, not data access or modification.
Summary
What happened
Uncontrolled resource consumption in Red Hat Undertow allows remote attackers to interrupt HTTP/2 service through flow-control handling. The HTTP/2 receive-flow-control path inadequately limits client-driven activity because the earlier correction for the same condition was incomplete. An unauthenticated network client must reach an HTTP/2-enabled listener; the documented impact is server overhead or denial of service, not data access or modification.
The record
- CVE
- CVE-2022-1259
- Published
- Aug 31, 2022
- Updated
- Aug 2, 2024
- Vendor
- Red Hat
- Product
- Undertow
- Classifications
- CWE-770, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 31, 2022CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Fixed in 2.3.0.Final, 2.2.17.SP1, 2.2.20.Final, 2.2.19.SP1.
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