In Eclipse Jetty Server, all 9.x versions, on webapps deployed using default Error Handling, when an intentionally bad query arrives that do
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 9.3.24, 9.4.11, 9.4.11.v20180605, 9.3.24.v20180605
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- The Eclipse Foundation Eclipse Jetty
through 9.2.0; From 9.3.0; fixed in 9.3.24; From 9.4.0; fixed in 9.4.11
- org.eclipse.jetty:jetty-serverMaven
From 9.4.0 · fixed in 9.4.11.v20180605
- org.eclipse.jetty:jetty-serverMaven
From 9.0.0 · fixed in 9.3.24.v20180605