Jetty vulnerable to authorization bypass due to inconsistent HTTP request handling (HTTP Request Smuggling)
The Eclipse Foundation Eclipse Jetty
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.eclipse.jetty:jetty-server Maven |
|
|
The Eclipse Foundation Eclipse Jetty
| Product | Affected | Fixed in |
|---|---|---|
| org.eclipse.jetty:jetty-server Maven |
|
|
In Eclipse Jetty Server, versions 9.2.x and older, 9.3.x (all non HTTP/1.x configurations), and 9.4.x (all HTTP/1.x configurations), when presented with two content-lengths headers, Jetty ignored the second. When presented with a content-length and a chunked encoding header, the content-length was ignored (as per RFC 2616). If an intermediary decided on the shorter length, but still passed on the longer body, then body content could be interpreted by Jetty as a pipelined request. If the intermediary was imposing authorization, the fake pipelined request would bypass that authorization.
From the CVE record · eclipse
Affected Eclipse Jetty Server configurations handle conflicting request-length headers in a way that can let body content be interpreted as a pipelined request. A remote attacker could bypass authorization imposed by an intermediary if it chooses the shorter request length but forwards the longer body. The issue affects Jetty 9.2.x and older, 9.3.x in non-HTTP/1.x configurations, and 9.4.x in HTTP/1.x configurations.
Engineers running Eclipse Jetty Server or Maven org.eclipse.jetty:jetty-server before 9.2.25.v20180606, from 9.3.0 to before 9.3.24.v20180605, or from 9.4.0 to before 9.4.11.v20180605 should check their configurations.