Unauthenticated request smuggling via LF-only headers
Published Nov 3, 2021 · Updated Aug 4, 2024
HTTP request smuggling in Apache Traffic Server 8.0.0 through 8.1.2 and 9.0.0 through 9.1.0 allows remote attackers to inject requests. The MIME header parser marks LF-terminated fields as raw-printable, so forwarding preserves a lone LF instead of emitting the required CRLF delimiter. No authentication or user interaction is required; inconsistent parsing by Traffic Server and another HTTP hop can route an injected request as a separate message.
Summary
What happened
HTTP request smuggling in Apache Traffic Server 8.0.0 through 8.1.2 and 9.0.0 through 9.1.0 allows remote attackers to inject requests. The MIME header parser marks LF-terminated fields as raw-printable, so forwarding preserves a lone LF instead of emitting the required CRLF delimiter. No authentication or user interaction is required; inconsistent parsing by Traffic Server and another HTTP hop can route an injected request as a separate message.
The record
- CVE
- CVE-2021-37147
- Published
- Nov 3, 2021
- Updated
- Aug 4, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Traffic Server
- Classifications
- CWE-444, CWE-20, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 3, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=8.0.0 to 8.1.2 and 9.0.0 to 9.1.0
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