Request smuggling via chunked-body byte overconsumption
Published Mar 23, 2020 · Updated Aug 5, 2024
HTTP request smuggling in Apache Traffic Server allows remote attackers to inject requests through crafted chunked bodies. The HTTP tunnel miscalculates the final byte count for an initially buffered chunked body and lets a consumer read beyond that message boundary. An unauthenticated network client can desynchronize Traffic Server from an origin on a reused connection, causing appended bytes to be handled as a separate request.
Summary
What happened
HTTP request smuggling in Apache Traffic Server allows remote attackers to inject requests through crafted chunked bodies. The HTTP tunnel miscalculates the final byte count for an initially buffered chunked body and lets a consumer read beyond that message boundary. An unauthenticated network client can desynchronize Traffic Server from an origin on a reused connection, causing appended bytes to be handled as a separate request.
The record
- CVE
- CVE-2019-17565
- Published
- Mar 23, 2020
- Updated
- Aug 5, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Traffic Server
- Classifications
- CWE-444, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 23, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=Apache Traffic Server 6.0.0 to 6.2.3, 7.0.0 to 7.1.8, and 8.0.0 to 8.0.5
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