Request smuggling via unclosed inbound connections
Published Mar 14, 2022 · Updated Aug 3, 2024
HTTP request smuggling in Apache HTTP Server 2.4.52 and earlier allows remote attackers to desynchronize request processing. The request-body discard error path leaves the inbound connection open instead of making it non-reusable, so trailing bytes can become a subsequent request. Exploitation requires a crafted body that triggers a discard error and connection reuse; the smuggled request crosses normal request boundaries.
Summary
What happened
HTTP request smuggling in Apache HTTP Server 2.4.52 and earlier allows remote attackers to desynchronize request processing. The request-body discard error path leaves the inbound connection open instead of making it non-reusable, so trailing bytes can become a subsequent request. Exploitation requires a crafted body that triggers a discard error and connection reuse; the smuggled request crosses normal request boundaries.
The record
- CVE
- CVE-2022-22720
- Published
- Mar 14, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache HTTP Server
- Classifications
- CWE-444, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 14, 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=Apache HTTP Server 2.4 <=2.4.52
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