Request smuggling via HTTP/1 connection reuse
Published Jan 26, 2022 · Updated Aug 3, 2024
Request smuggling in Varnish Cache before 6.6.2 allows remote attackers to inject an extra HTTP/1 request via a reused client connection. Varnish treats the smuggled bytes as an additional request, processes them through VCL, and returns a spurious response on the client connection. The attack requires network access to an HTTP/1 connection and can alter response integrity or disclose data handled by the injected request.
Summary
What happened
Request smuggling in Varnish Cache before 6.6.2 allows remote attackers to inject an extra HTTP/1 request via a reused client connection. Varnish treats the smuggled bytes as an additional request, processes them through VCL, and returns a spurious response on the client connection. The attack requires network access to an HTTP/1 connection and can alter response integrity or disclose data handled by the injected request.
The record
- CVE
- CVE-2022-23959
- Published
- Jan 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-444, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 26, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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