CVE-2019-20445Published Jan 29, 2020 · Jan 29Updated Oct 24
HTTP Request Smuggling in Netty
Critical9.1Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| io.netty:netty-handler Maven |
|
|
| org.jboss.netty:netty Maven |
| No fix yet |
| io.netty:netty Maven |
|
| Product | Affected | Fixed in |
|---|---|---|
| io.netty:netty-handler Maven |
|
|
| org.jboss.netty:netty Maven |
| No fix yet |
| io.netty:netty Maven |
|
| No fix yet |
HttpObjectDecoder.java in Netty before 4.1.44 allows a Content-Length header to be accompanied by a second Content-Length header, or by a Transfer-Encoding header.
From the CVE record · mitre
Netty's HttpObjectDecoder accepts a Content-Length header alongside a second Content-Length header or a Transfer-Encoding header. An attacker who can send HTTP messages to an affected application can supply these conflicting headers. The input does not specify whether authentication or user interaction is required.
Engineers using Maven io.netty:netty-handler versions 4.0.0 through versions before 4.1.45, or any version of org.jboss.netty:netty or io.netty:netty, should check their dependencies.