Bug 1597418 (CVE-2018-12536) - CVE-2018-12536 jetty: full server path revealed when using the default Error Handling
Summary: CVE-2018-12536 jetty: full server path revealed when using the default Error ...
Alias: CVE-2018-12536
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1597419
Blocks: 1597422
TreeView+ depends on / blocked
Reported: 2018-07-02 21:59 UTC by Laura Pardo
Modified: 2021-10-27 10:54 UTC (History)
13 users (show)

Fixed In Version: jetty 9.3.24.v20180605, jetty 9.4.11.v20180605
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-10-27 10:54:44 UTC

Attachments (Terms of Use)

Description Laura Pardo 2018-07-02 21:59:06 UTC
A flaw was found 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.


Comment 1 Laura Pardo 2018-07-02 22:00:23 UTC
Created jetty tracking bugs for this issue:

Affects: fedora-all [bug 1597419]

Comment 3 Doran Moppert 2018-09-20 06:34:13 UTC

Information disclosure occurs when java.nio.file.InvalidPathException occurs and is handled by the default Jetty error handler. To protect against this, a custom error handler can be configured for that particular error or for a larger set of errors according to the documentation link below. Red Hat Product Security advises that production deployments on Jetty use custom error handlers to limit the information disclosed and to ensure effective logging of error conditions.


Note You need to log in before you can comment on or make changes to this bug.