Unspecified impact via malformed HTTP/1.1 headers
Published Aug 10, 2022 · Updated Aug 3, 2024
Improper input validation in Apache Traffic Server 8.0.0 through 9.1.2 allows remote attackers to submit malformed HTTP/1.1 headers. Apache has not published the specific parser locus, rejected grammar, or wrong operation performed on malformed header input. The exposed proxy listener is the gate; public material does not establish the resulting downstream effect.
Summary
What happened
Improper input validation in Apache Traffic Server 8.0.0 through 9.1.2 allows remote attackers to submit malformed HTTP/1.1 headers. Apache has not published the specific parser locus, rejected grammar, or wrong operation performed on malformed header input. The exposed proxy listener is the gate; public material does not establish the resulting downstream effect.
The record
- CVE
- CVE-2022-28129
- Published
- Aug 10, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Traffic Server
- Classifications
- CWE-20
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 10, 2022CVE 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=8.0.0 to 9.1.2
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