Cache poisoning via forwarded URL fragments
Published Jun 29, 2021 · Updated Aug 3, 2024
URL-fragment handling in Apache Traffic Server affected releases allows remote attackers to poison shared cache entries via crafted requests. HttpTransact::build_request retained a client-supplied fragment when constructing the upstream request instead of removing the client-only component. An unauthenticated network request can therefore make the proxy cache origin content under a mismatched URL, compromising later responses served from that shared cache.
Summary
What happened
URL-fragment handling in Apache Traffic Server affected releases allows remote attackers to poison shared cache entries via crafted requests. HttpTransact::build_request retained a client-supplied fragment when constructing the upstream request instead of removing the client-only component. An unauthenticated network request can therefore make the proxy cache origin content under a mismatched URL, compromising later responses served from that shared cache.
The record
- CVE
- CVE-2021-27577
- Published
- Jun 29, 2021
- Updated
- Aug 3, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Traffic Server
- Classifications
- CWE-444, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 29, 2021CVE 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=Apache Traffic Server 7.0.0 to 7.1.12, 8.0.0 to 8.1.1, 9.0.0 to 9.0.1
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