MediumGHSA-xc67-hjx6-cgg6CVE-2019-10247

Installation information leak in Eclipse Jetty

Published 23 Apr 2019 · Updated 14 Mar 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
>=7.0.0 <9.2.28.v20190418
Fixed in
9.2.28.v20190418
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.28.v20190418 -DforceVersion=true
Affected
>=9.3.0 <9.3.27.v20190418
Fixed in
9.3.27.v20190418
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.27.v20190418 -DforceVersion=true
Affected
>=9.4.0 <9.4.17.v20190418
Fixed in
9.4.17.v20190418
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.17.v20190418 -DforceVersion=true

Details

In Eclipse Jetty version 7.x, 8.x, 9.2.27 and older, 9.3.26 and older, and 9.4.16 and older, the server running on any OS and Jetty version combination will reveal the configured fully qualified directory base resource location on the output of the 404 error for not finding a Context that matches the requested path. The default server behavior on jetty-distribution and jetty-home will include at the end of the Handler tree a DefaultHandler, which is responsible for reporting this 404 error, it presents the various configured contexts as HTML for users to click through to. This produced HTML includes output that contains the configured fully qualified directory base resource location for each context.

Is GHSA-xc67-hjx6-cgg6 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.