Skip to content

Jetty vulnerable to authorization bypass due to inconsistent HTTP request handling (HTTP Request Smuggling)

Critical severity GitHub Reviewed Published Oct 19, 2018 to the GitHub Advisory Database • Updated Mar 9, 2023

Package

maven org.eclipse.jetty:jetty-server (Maven)

Affected versions

< 9.2.25.v20180606
>= 9.3.0, < 9.3.24.v20180605
>= 9.4.0, < 9.4.11.v20180605

Patched versions

9.2.25.v20180606
9.3.24.v20180605
9.4.11.v20180605

Description

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), are vulnerable to HTTP Request Smuggling when presented with two content-lengths headers, allowing authorization bypass. When presented with a content-length and a chunked encoding header, the content-length was ignored (as per RFC 2616). If an intermediary decides on the shorter length, but still passes on the longer body, then body content could be interpreted by Jetty as a pipelined request. If the intermediary is imposing authorization, the fake pipelined request bypasses that authorization.

References

Published by the National Vulnerability Database Jun 26, 2018
Published to the GitHub Advisory Database Oct 19, 2018
Reviewed Jun 16, 2020
Last updated Mar 9, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

1.089%
(85th percentile)

Weaknesses

CVE ID

CVE-2017-7658

GHSA ID

GHSA-6x9x-8qw9-9pp6

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.