HTTP request smuggling via stripped header control characters
Published Dec 9, 2021 · Updated Aug 4, 2024
HTTP request smuggling in Netty before 4.1.71.Final allows remote attackers to alter backend requests through malformed header names. HttpObjectDecoder.splitHeader treats non-OWS control characters as ignorable whitespace and strips them instead of rejecting the header. The flaw is reachable when a Netty-based proxy forwards the sanitized request to a backend, enabling inconsistent request interpretation without authentication.
Summary
What happened
HTTP request smuggling in Netty before 4.1.71.Final allows remote attackers to alter backend requests through malformed header names. HttpObjectDecoder.splitHeader treats non-OWS control characters as ignorable whitespace and strips them instead of rejecting the header. The flaw is reachable when a Netty-based proxy forwards the sanitized request to a backend, enabling inconsistent request interpretation without authentication.
The record
- CVE
- CVE-2021-43797
- Published
- Dec 9, 2021
- Updated
- Aug 4, 2024
- Vendor
- The Netty Project
- Product
- Netty
- Classifications
- CWE-444, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 9, 2021CVE publishedPublication date reported by the CVE source.
- 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.7.0.Final
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