Skip to content
Fencer Vulns
medium 5.3

CVE-2018-12536 json

Eclipse Jetty Server generates error message containing sensitive information

published 2018-06-27 8 y ago modified 2026-06-17 4 mo ago also GHSA-9rgv-h7x4-qw8g , EUVD-2018-0567

cvss
5.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.2%
EPSS 4.2% chance of exploitation in 30 days, percentile 91%
public exploits
0
none known

Summary

In Eclipse Jetty Server, all 9.x versions, on webapps deployed using default Error Handling, when an intentionally bad query arrives that doesn't match a dynamic url-pattern, and is eventually handled by the DefaultServlet's static file serving, the bad characters can trigger a java.nio.file.InvalidPathException which includes the full path to the base resource directory that the DefaultServlet and/or webapp is using. If this InvalidPathException is then handled by the default Error Handler, the InvalidPathException message is included in the error response, revealing the full server path to the requesting system.

Patch / fix

  • maven org.eclipse.jetty:jetty-server 9.3.24.v20180605, 9.4.11.v20180605
  • The Eclipse Foundation Eclipse Jetty 9.3.24, 9.4.11
  • jetty9 Debian 14, Debian 13, Debian 12 9.2.25-1

debian advisories DEBIAN-CVE-2018-12536

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-12536 updated cvss 3.7

jetty: full server path revealed when using the default Error Handling

  • Red Hat Enterprise Linux 7 jetty-io, jetty-ant, jetty-jmx, jetty-jsp, jetty-xml, jetty-http, +30 more
    affected: workaround, no fix planned “Will not fix”
  • Red Hat Fuse 7 jetty
    affected: workaround, no fix available
  • Red Hat JBoss Fuse 6 jetty Red Hat Satellite 5 jetty-project Red Hat Software Collections rh-java-common-jetty-io, rh-java-common-jetty-ant, rh-java-common-jetty-jmx, rh-java-common-jetty-jsp, rh-java-common-jetty-xml, rh-java-common-jetty-http, +30 more
    affected: workaround, no fix planned “Will not fix”
  • Red Hat Fuse 7.6.0
    fixed: vendor fix RHSA-2020:0983
  • Red Hat Enterprise Linux 6 jetty-eclipse
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

4.23% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.eclipse.jetty:jetty-server
>=9.4.0, <9.4.11.v20180605
>=9.0.0, <9.3.24.v20180605
9.4.11.v20180605
9.3.24.v20180605

Affected products

  • The Eclipse Foundation Eclipse Jetty

Classification

Weakness
  • CWE-209 Generation of Error Message Containing Sensitive Information

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.