In Eclipse Jetty Server, all 9.x versions, on webapps deployed using default Error Handling, when an intentionally bad query arrives that…
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 4%. Fixed in 9.3.24, 9.4.11 and unspecified.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| The Eclipse Foundation | <9.3.24, <9.4.11, <=9.2.0, >=9.3.0 <unspecified, >=9.4.0 <unspecified | 9.3.24, 9.4.11, unspecified |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket