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.
How to fix
- eclipse jetty9.3.24, 9.4.11 or later
- org.eclipse.jetty:jetty-server9.4.11.v20180605, 9.3.24.v20180605 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| eclipse jetty | 9.0.0 ≤ v ≤ 9.2.26, 9.3.0 ≤ v < 9.3.24, 9.4.0 ≤ v < 9.4.11 | 9.3.24, 9.4.11 |
| oracle retail_xstore_point_of_service | 7.1, 15.0, 16.0.0, 17.0 | — |
| org.eclipse.jetty:jetty-serverMaven | 9.4.0 ≤ v < 9.4.11.v20180605, 9.0.0 ≤ v < 9.3.24.v20180605 | 9.4.11.v20180605, 9.3.24.v20180605 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.