Eclipse Jetty Server generates error message containing sensitive information
Moderate severity
GitHub Reviewed
Published
Oct 19, 2018
to the GitHub Advisory Database
•
Updated Aug 18, 2023
Package
Affected versions
>= 9.4.0, <= 9.4.10.v20180503
>= 9.0.0, <= 9.3.23.v20180228
Patched versions
9.4.11.v20180605
9.3.24.v20180605
Description
Published by the National Vulnerability Database
Jun 27, 2018
Published to the GitHub Advisory Database
Oct 19, 2018
Reviewed
Jun 16, 2020
Last updated
Aug 18, 2023
Credits
-
joshbressers Analyst
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