CVE-2018-12536
moderate-risk
Published 2018-06-27
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.
Do I need to act?
~
3.3% chance of exploitation in next 30 days
EPSS score — moderate exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
5
CVSS 5.3/10
Medium
NETWORK
/ LOW complexity
Affected Products (5)
References (16)
Third Party Advisory
http://www.securitytracker.com/id/1041194
Vendor Advisory
https://bugs.eclipse.org/bugs/show_bug.cgi?id=535670
Third Party Advisory
https://security.netapp.com/advisory/ntap-20181014-0001/
Third Party Advisory
https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpe...
Third Party Advisory
http://www.securitytracker.com/id/1041194
Vendor Advisory
https://bugs.eclipse.org/bugs/show_bug.cgi?id=535670
Third Party Advisory
https://security.netapp.com/advisory/ntap-20181014-0001/
Third Party Advisory
https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpe...
40
/ 100
moderate-risk
Severity
21/34 · High
Exploitability
7/34 · Low
Exposure
12/34 · Low