Denial of service via reusable double AJP response
Published Aug 31, 2022 · Updated Aug 3, 2024
Unchecked response handling in Red Hat Undertow allows remote attackers to interrupt AJP service after an HTTP 400 response. AjpReadListener.handleEvent emits an extra bad-request response and marks END_RESPONSE reusable even though it closes the connection. An exposed AJP listener is required; subsequent CPING reuse consumes the stale SEND_HEADERS packet instead of CPONG, disrupting service.
Summary
What happened
Unchecked response handling in Red Hat Undertow allows remote attackers to interrupt AJP service after an HTTP 400 response. AjpReadListener.handleEvent emits an extra bad-request response and marks END_RESPONSE reusable even though it closes the connection. An exposed AJP listener is required; subsequent CPING reuse consumes the stale SEND_HEADERS packet instead of CPONG, disrupting service.
The record
- CVE
- CVE-2022-1319
- Published
- Aug 31, 2022
- Updated
- Aug 3, 2024
- Vendor
- Red Hat
- Product
- Undertow
- Classifications
- CWE-252, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 31, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.18.Final, 2.2.17.SP3, 2.2.17.SP4, 2.3.0.Alpha2
What conditions does exploitation require?
What is affected?
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.
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