VYPR
Moderate severityNVD Advisory· Published Jun 27, 2018· Updated Aug 5, 2024

CVE-2018-12536

CVE-2018-12536

Description

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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A specially crafted HTTP query to Eclipse Jetty's DefaultServlet triggers an InvalidPathException that discloses the full server path in the error response.

Vulnerability

In Eclipse Jetty versions 9.2.x and older, 9.3.x (all configurations), and 9.4.x (all configurations), web applications deployed with the default error handling mechanism are vulnerable to an information disclosure issue. When a crafted HTTP query with malformed characters that does not match any servlet’s dynamic URL pattern is processed by the static file serving DefaultServlet, it causes a java.nio.file.InvalidPathException whose message includes the full filesystem path to the base resource directory used by the DefaultServlet or webapp [1][2].

Exploitation

An attacker requires no authentication and only needs network access to a vulnerable Jetty instance. The attacker sends an HTTP request with an intentionally malformed query string (e.g., containing non-printable or illegal characters) that fails to match any dynamic URL pattern. The request is eventually handled by the DefaultServlet for static file serving, where the malformed path triggers the InvalidPathException. This exception is then caught and processed by the default error handler, which includes the exception’s message (containing the full server path) in the HTTP error response [2].

Impact

A successful exploitation results in the disclosure of the full server filesystem path of the base resource directory used by the DefaultServlet or the deployed web application. This path disclosure aids an attacker in performing further reconnaissance and potentially chaining with other attacks, such as path traversal or local file inclusion [2][3]. No other direct impact on confidentiality, integrity, or availability has been reported from this specific flaw.

Mitigation

The vulnerability is fixed in Jetty versions 9.3.24.v20180605 and 9.4.11.v20180605 [2]. For version 9.2.x and older (which are end-of-life), no patch is provided and users are strongly advised to upgrade to a supported release. A workaround for versions that cannot be immediately patched is to avoid using the default error handler by implementing a custom error handler that does not expose the InvalidPathException or the underlying stack trace [1][2].

AI Insight generated on May 22, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
org.eclipse.jetty:jetty-serverMaven
>= 9.4.0, < 9.4.11.v201806059.4.11.v20180605
org.eclipse.jetty:jetty-serverMaven
>= 9.0.0, < 9.3.24.v201806059.3.24.v20180605

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

13

News mentions

0

No linked articles in our index yet.