HTTP request smuggling in netty
### 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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2021-43797US | medium6.5 | — | ||
Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. Netty prior to version 4.1.71… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/netty/nettyWEB
- https://github.com/netty/netty/commit/07aa6b5938a8b6ed7a6586e066400e2643897323WEB
- https://github.com/netty/netty/pull/11891WEB
- https://github.com/netty/netty/security/advisories/GHSA-wx5j-54mm-rqqqWEB
- https://lists.debian.org/debian-lts-announce/2023/01/msg00008.htmlWEB
- https://nvd.nist.gov/vuln/detail/CVE-2021-43797ADVISORY
- https://security.netapp.com/advisory/ntap-20220107-0003WEB
- https://www.debian.org/security/2023/dsa-5316WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan