HTTP fails to validate against control chars in header names which may lead to HTTP request smuggling
netty
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| io.netty:netty-codec-http Maven |
|
|
| org.jboss.netty:netty Maven |
| No fix yet |
| io.netty:netty Maven |
|
netty
| Product | Affected | Fixed in |
|---|---|---|
| io.netty:netty-codec-http Maven |
|
|
| org.jboss.netty:netty Maven |
| No fix yet |
| io.netty:netty Maven |
|
| No fix yet |
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.Final skips control chars when they are present at the beginning / end of the header name. It should instead 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 therefore does not do the validation itself. Users should upgrade to version 4.1.71.Final.
From the CVE record · GitHub_M
Netty versions before 4.1.71.Final can skip control characters at the beginning or end of an HTTP header name instead of rejecting it. When Netty is used as a proxy, it may forward a sanitized header name to another remote system, potentially enabling HTTP request smuggling.
Engineers using Maven io.netty:netty-codec-http versions >=4.0.0 and <4.1.71.Final, or the listed org.jboss.netty:netty and io.netty:netty packages, should check their deployments.