CriticalGHSA-6x9x-8qw9-9pp6CVE-2017-7658

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

Published 19 Oct 2018 · Updated 16 Feb 2024

Is your project on an affected org.eclipse.jetty:jetty-server?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<9.2.25.v20180606
Fixed in
9.2.25.v20180606
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.eclipse.jetty:jetty-server -DdepVersion=9.2.25.v20180606 -DforceVersion=true
Affected
>=9.3.0 <9.3.24.v20180605
Fixed in
9.3.24.v20180605
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.eclipse.jetty:jetty-server -DdepVersion=9.3.24.v20180605 -DforceVersion=true
Affected
>=9.4.0 <9.4.11.v20180605
Fixed in
9.4.11.v20180605
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.eclipse.jetty:jetty-server -DdepVersion=9.4.11.v20180605 -DforceVersion=true

Details

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.

Is GHSA-6x9x-8qw9-9pp6 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.eclipse.jetty:jetty-server, and gives you the command that fixes it.

More advisories for org.eclipse.jetty:jetty-server

  • HighCVE-2024-7708Eclipse Jetty: DoS attack triggering OutOfMemory with 100-Continue requests · 22 Jul 2026
  • MediumCVE-2026-6790Eclipse Jetty: HTTP Authority/Host mismatch · 22 Jul 2026
  • MediumCVE-2026-10051Eclipse Jetty: Cross-Request Leakage for trailers on HTTP/1.1 keep-alive connections · 22 Jul 2026
  • HighCVE-2026-1605The Eclipse Jetty Server Artifact has a Gzip request memory leak · 5 Mar 2026
  • HighCVE-2024-13009**UNSUPPORTED WHEN ASSIGNED** GzipHandler causes part of request body to be seen as request body of a separate request · 8 May 2025
  • MediumCVE-2024-8184Eclipse Jetty's ThreadLimitHandler.getRemote() vulnerable to remote DoS attacks · 14 Oct 2024
All 29 advisories for org.eclipse.jetty:jetty-server

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.