GHSA-wx5j-54mm-rqqq
HTTP request smuggling in netty
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| Maven | io.netty:netty-codec-http | >= 4.0.0, < 4.1.71.Final | 4.1.71.Final |
| Maven | org.jboss.netty:netty | < 4.0.0 | no fix listed |
| Maven | io.netty:netty | < 4.0.0 | no fix listed |
Details
As written in the advisory (Markdown source, shown as plain text).
### Impact
Netty currently just skips control chars when these are present at the beginning / end of the header name. We should better fail fast as these are not allowed by the spec and could lead to HTTP request smuggling.
Failing to do the validation might cause netty to "sanitize" header names before it forward these to another remote system when used as proxy. This remote system can't see the invalid usage anymore and so not do the validation itself.
References
External links from the advisory. They lead to third-party sites.
- https://github.com/netty/netty/security/advisories/GHSA-wx5j-54mm-rqqq
- https://nvd.nist.gov/vuln/detail/CVE-2021-43797
- https://github.com/netty/netty/pull/11891
- https://github.com/netty/netty/commit/07aa6b5938a8b6ed7a6586e066400e2643897323
- https://github.com/netty/netty
- https://lists.debian.org/debian-lts-announce/2023/01/msg00008.html
- https://security.netapp.com/advisory/ntap-20220107-0003
- https://www.debian.org/security/2023/dsa-5316
- https://www.oracle.com/security-alerts/cpuapr2022.html
- https://www.oracle.com/security-alerts/cpujul2022.html