Request disruption via undrained cached-request body
Published Dec 19, 2022 · Updated Apr 17, 2025
Request-handling error in Apache Traffic Server 8.0.0 through 8.1.5 and 9.0.0 through 9.1.3 lets remote attackers disrupt later requests. On a conditional-GET cache hit, the cache no-op path returns without draining the request body, leaving its bytes on the connection. Exploitation requires a cached object and connection reuse; the leftover bytes are parsed as the next request and can produce a 400 response for another client.
Summary
What happened
Request-handling error in Apache Traffic Server 8.0.0 through 8.1.5 and 9.0.0 through 9.1.3 lets remote attackers disrupt later requests. On a conditional-GET cache hit, the cache no-op path returns without draining the request body, leaving its bytes on the connection. Exploitation requires a cached object and connection reuse; the leftover bytes are parsed as the next request and can produce a 400 response for another client.
The record
- CVE
- CVE-2022-37392
- Published
- Dec 19, 2022
- Updated
- Apr 17, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache Traffic Server
- Classifications
- CWE-754, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 19, 2022CVE publishedPublication date reported by the CVE source.
- Apr 17, 2025Record 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=8.0.0 <=9.1.3
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.
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