HTTP request splitting via duplicate Content-Length
Published Sep 29, 2021 · Updated Aug 4, 2024
HTTP request splitting in Zeek 4.1.0 allows remote attackers to invalidate HTTP-based security analysis via crafted requests. The HTTP analyzer treats repeated Content-Length headers as separate message boundaries, splitting one input into multiple records with misplaced methods, hosts, and URIs. The attack requires network access to traffic monitored by Zeek and can corrupt analysis and logs; the vendor disputes that this behavior is a vulnerability and considers it intended.
Summary
What happened
HTTP request splitting in Zeek 4.1.0 allows remote attackers to invalidate HTTP-based security analysis via crafted requests. The HTTP analyzer treats repeated Content-Length headers as separate message boundaries, splitting one input into multiple records with misplaced methods, hosts, and URIs. The attack requires network access to traffic monitored by Zeek and can corrupt analysis and logs; the vendor disputes that this behavior is a vulnerability and considers it intended.
The record
- CVE
- CVE-2021-41732
- Published
- Sep 29, 2021
- Updated
- Aug 4, 2024
- Vendor
- Zeek Project
- Product
- Zeek
- Classifications
- CWE-444, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 29, 2021CVE publishedPublication date reported by the CVE source.
- May 1, 2024Exploitation reportedCISA SSVC proof-of-concept assessment
- Aug 4, 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=4.1.0
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
- Zeek HTTP request splitting proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- CISA SSVC proof-of-concept assessmentreported exploitation
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