Skip to content

Critical severity vulnerability that affects org.eclipse.jetty:jetty-server

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

Package

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

Affected versions

<= 9.2.25.v20180105
>= 9.3.0, <= 9.3.23.v20180228

Patched versions

9.2.25.v20180606
9.3.24.v20180605

Description

In Eclipse Jetty, versions 9.2.x and older, 9.3.x, transfer-encoding chunks are handled poorly. The chunk length parsing was vulnerable to an integer overflow. Thus a large chunk size could be interpreted as a smaller chunk size and content sent as chunk body could be interpreted as a pipelined request. If Jetty was deployed behind an intermediary that imposed some authorization and that intermediary allowed arbitrarily large chunks to be passed on unchanged, then this flaw could be used to bypass the authorization imposed by the intermediary as the fake pipelined request would not be interpreted by the intermediary as a request.

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 Feb 1, 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

0.731%
(81st percentile)

Weaknesses

CVE ID

CVE-2017-7657

GHSA ID

GHSA-vgg8-72f2-qm23

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.