Request smuggling via malformed field names
Published Jul 26, 2024 · Updated Nov 3, 2025
HTTP request smuggling in Apache Traffic Server 8.0.0 through 8.1.10 and 9.0.0 through 9.2.4 allows remote attackers to poison caches. The request-header parser accepts disallowed field-name characters instead of rejecting the request, then forwards the malformed field to an origin server. Exploitation requires an origin server that interprets the invalid field differently; the resulting desynchronization can route a hidden request or corrupt cached responses.
Summary
What happened
HTTP request smuggling in Apache Traffic Server 8.0.0 through 8.1.10 and 9.0.0 through 9.2.4 allows remote attackers to poison caches. The request-header parser accepts disallowed field-name characters instead of rejecting the request, then forwards the malformed field to an origin server. Exploitation requires an origin server that interprets the invalid field differently; the resulting desynchronization can route a hidden request or corrupt cached responses.
The record
- CVE
- CVE-2023-38522
- Published
- Jul 26, 2024
- Updated
- Nov 3, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache Traffic Server
- Classifications
- CWE-444, CAPEC-33, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 26, 2024CVE publishedPublication date reported by the CVE source.
- Nov 3, 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 <=8.1.10
- Affected versionversion=9.0.0 <=9.2.4
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