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 pr

Summary

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.

Timeline

1. Jun 26, 2018, 5: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

  fixed in 9.2.25; 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

• org.eclipse.jetty:jetty-serverMaven

  From 9.4.0 · fixed in 9.4.11.v20180605

References 17