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.
Metrics
Affected Vendors & Products
Advisories
Source | ID | Title |
---|---|---|
![]() |
DSA-4278-1 | jetty9 security update |
![]() |
EUVD-2018-0526 | 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. |
![]() |
GHSA-6x9x-8qw9-9pp6 | Jetty vulnerable to authorization bypass due to inconsistent HTTP request handling (HTTP Request Smuggling) |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.

Status: PUBLISHED
Assigner: eclipse
Published:
Updated: 2024-08-05T16:12:27.826Z
Reserved: 2017-04-11T00:00:00
Link: CVE-2017-7658

No data.

Status : Modified
Published: 2018-06-26T17:29:00.210
Modified: 2024-11-21T03:32:23.850
Link: CVE-2017-7658


No data.