VYPR
Critical severityNVD Advisory· Published Jun 26, 2018· Updated Aug 5, 2024

CVE-2017-7657

CVE-2017-7657

Description

In Eclipse Jetty, versions 9.2.x and older, 9.3.x (all configurations), and 9.4.x (non-default configuration with RFC2616 compliance enabled), 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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

In Eclipse Jetty, a chunk length integer overflow allows request smuggling, potentially bypassing authorization when behind an intermediary.

Vulnerability

In Eclipse Jetty, versions 9.2.x and older, 9.3.x (all configurations), and 9.4.x (non-default configuration with RFC2616 compliance enabled), the transfer-encoding chunk length parsing is vulnerable to an integer overflow [1]. This flaw causes a large chunk size to be misinterpreted as a smaller one, allowing the chunk body to be treated as a pipelined HTTP request [2].

Exploitation

An attacker requires a specific intermediary that imposes authorization but allows arbitrarily large chunks to pass unchanged. By crafting a chunked transfer-encoding message with an oversized chunk length, the attacker can trigger the overflow, resulting in a pipelined request that the intermediary does not recognize as a request, thus bypassing its authorization [1][2].

Impact

Successful exploitation could allow HTTP request smuggling, leading to authorization bypass and potential access to restricted resources. The impact can be significant as the intermediary's security controls are circumvented [2].

Mitigation

Fixed versions are available: 9.2.25.v20180606, 9.3.24.v20180605, and 9.4.11.v20180605 [2][4]. For 9.4.x, disabling RFC2616 compliance (non-default) also mitigates the issue. Users should upgrade to the latest patched version or apply the configuration change [1].

AI Insight generated on May 22, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
org.eclipse.jetty:jetty-serverMaven
< 9.2.25.v201806069.2.25.v20180606
org.eclipse.jetty:jetty-serverMaven
>= 9.3.0, < 9.3.24.v201806059.3.24.v20180605

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

26

News mentions

0

No linked articles in our index yet.