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

Summary

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.

Timeline

1. Jun 26, 2018, 4:00 PM UTCCVE published
2. Aug 5, 2024, 4:12 PM UTCRecord last updated
3. Oct 28, 2026EPSS reached 10%

   FIRST estimates at least a 10% chance of exploitation in the next 30 days

Affected versions

• The Eclipse Foundation Eclipse Jetty

  through 9.2.0; From 9.3.0; fixed in 9.3.24; From 9.4.0; fixed in 9.4.11

• org.eclipse.jetty:jetty-serverMaven

  fixed in 9.2.25.v20180606

• org.eclipse.jetty:jetty-serverMaven

  From 9.3.0 · fixed in 9.3.24.v20180605

References 16