Io.netty/netty-codec-http: netty split transfer-encoding fields bypass final-chunked validation and enable request smuggling
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
A flaw was found in Netty's HTTP/1.1 decoder. This vulnerability allows a remote attacker to bypass `Transfer-Encoding` header validation by splitting the `Transfer-Encoding` field across multiple headers, with the last field containing a non-final transfer coding like `gzip` or `deflate`. This bypass can lead to HTTP request smuggling, enabling attackers to bypass security controls, desynchronize request processing, or cause requests to be processed in an unintended context.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- netty-codec-http
Version range not reported
- netty-codec-http
Version range not reported
- netty-codec-http
Version range not reported
- netty-codec-http
Version range not reported
- netty-codec-http
Version range not reported
- netty-codec-http
Version range not reported
- netty-codec-http
Version range not reported
- netty-codec-http
Version range not reported
- netty-codec-http
Version range not reported
- netty-codec-http
Version range not reported
- netty-codec-http
Version range not reported
- netty-codec-http
Version range not reported
- netty-codec-http
Version range not reported
- netty-codec-http
Version range not reported