CVE-2018-12536
published 2018-06-27CVE-2018-12536: 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…
PriorityP430medium5.3CVSS 3.1
AVNACLPRNUINSUCLINAN
EPSS
4.33%
90.1th percentile
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.
Affected
13 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | jetty9 | < jetty9 9.2.25-1 (bookworm) | jetty9 9.2.25-1 (bookworm) |
| eclipse | jetty | 9.0.0 – 9.2.26 | — |
| eclipse | jetty | >= 9.3.0 < 9.3.24 | 9.3.24 |
| eclipse | jetty | >= 9.4.0 < 9.4.11 | 9.4.11 |
| oracle | retail_xstore_point_of_service | — | — |
| oracle | retail_xstore_point_of_service | — | — |
| oracle | retail_xstore_point_of_service | — | — |
| oracle | retail_xstore_point_of_service | — | — |
| the_eclipse_foundation | eclipse_jetty | >= 9.3.0 < unspecified | unspecified |
| the_eclipse_foundation | eclipse_jetty | >= 9.4.0 < unspecified | unspecified |
| the_eclipse_foundation | eclipse_jetty | >= unspecified < 9.3.24 | 9.3.24 |
| the_eclipse_foundation | eclipse_jetty | >= unspecified < 9.4.11 | 9.4.11 |
| the_eclipse_foundation | eclipse_jetty | unspecified – 9.2.0 | — |
CVSS provenance
nvdv3.15.3MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:P/I:N/A:N
osv5.3MEDIUM
vendor_debian5.3LOW
vendor_redhat5.3MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
Eclipse Jetty Server generates error message containing sensitive information
ghsa·2018-10-19
CVE-2018-12536 [MEDIUM] CWE-209 Eclipse Jetty Server generates error message containing sensitive information
Eclipse Jetty Server generates error message containing sensitive information
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.
OSV
Eclipse Jetty Server generates error message containing sensitive information
osv·2018-10-19
CVE-2018-12536 [MEDIUM] Eclipse Jetty Server generates error message containing sensitive information
Eclipse Jetty Server generates error message containing sensitive information
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.
OSV
CVE-2018-12536: In Eclipse Jetty Server, all 9
osv·2018-06-27·CVSS 5.3
CVE-2018-12536 [MEDIUM] CVE-2018-12536: In Eclipse Jetty Server, all 9
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.
Red Hat
jetty: full server path revealed when using the default Error Handling
vendor_redhat·2018-06-27·CVSS 5.3
CVE-2018-12536 [MEDIUM] CWE-209 jetty: full server path revealed when using the default Error Handling
jetty: full server path revealed when using the default Error Handling
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.
Mitigation: Information disclosure occurs when java.nio.file.InvalidPathException occurs and is handled b
Debian
CVE-2018-12536: jetty9 - In Eclipse Jetty Server, all 9.x versions, on webapps deployed using default Err...
vendor_debian·2018·CVSS 5.3
CVE-2018-12536 [MEDIUM] CVE-2018-12536: jetty9 - In Eclipse Jetty Server, all 9.x versions, on webapps deployed using default Err...
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.
Scope: local
bookworm: resolved (fixed in 9.2.25-1)
bullseye: resolved (fixed in 9.2.25-1)
forky: resolved (fixed in 9.2.25-1)
sid: resolved (fixed in 9.2.25-1)
trixie: resolved
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2018-12536 jetty: full server path revealed when using the default Error Handling
bugzilla·2018-07-02·CVSS 5.3
CVE-2018-12536 [MEDIUM] CVE-2018-12536 jetty: full server path revealed when using the default Error Handling
CVE-2018-12536 jetty: full server path revealed when using the default Error Handling
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.
References:
http://www.securitytracker.com/id/1041194
https://bugs.eclip
Bugzilla
CVE-2018-12536 jetty: full server path revealed when using the default Error Handling [fedora-all]
bugzilla·2018-07-02·CVSS 5.3
CVE-2018-12536 [MEDIUM] CVE-2018-12536 jetty: full server path revealed when using the default Error Handling [fedora-all]
CVE-2018-12536 jetty: full server path revealed when using the default Error Handling [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multip
http://www.securitytracker.com/id/1041194https://bugs.eclipse.org/bugs/show_bug.cgi?id=535670https://lists.apache.org/thread.html/053d9ce4d579b02203db18545fee5e33f35f2932885459b74d1e4272%40%3Cissues.activemq.apache.org%3Ehttps://lists.debian.org/debian-lts-announce/2021/05/msg00016.htmlhttps://security.netapp.com/advisory/ntap-20181014-0001/https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbst03953en_ushttps://www.oracle.com/security-alerts/cpuoct2020.htmlhttps://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.htmlhttp://www.securitytracker.com/id/1041194https://bugs.eclipse.org/bugs/show_bug.cgi?id=535670https://lists.apache.org/thread.html/053d9ce4d579b02203db18545fee5e33f35f2932885459b74d1e4272%40%3Cissues.activemq.apache.org%3Ehttps://lists.debian.org/debian-lts-announce/2021/05/msg00016.htmlhttps://security.netapp.com/advisory/ntap-20181014-0001/https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbst03953en_ushttps://www.oracle.com/security-alerts/cpuoct2020.htmlhttps://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html
2018-06-27
Published