In Eclipse Jetty Server, all 9.x versions, on webapps deployed using default Error Handling, when an intentionally bad query arrives that doesnt match a dynamic url-pattern, and is eventually handled by the DefaultServlets 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.
The product generates an error message that includes sensitive information about its environment, users, or associated data.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Jetty | Eclipse | 9.0.0 (including) | 9.2.26 (including) |
| Jetty | Eclipse | 9.3.0 (including) | 9.3.24 (excluding) |
| Jetty | Eclipse | 9.4.0 (including) | 9.4.11 (excluding) |
| Red Hat Fuse 7.6.0 | RedHat | * | |
| Jetty8 | Ubuntu | trusty | * |
| Jetty9 | Ubuntu | artful | * |
| Jetty9 | Ubuntu | esm-apps/xenial | * |
| Jetty9 | Ubuntu | upstream | * |
| Jetty9 | Ubuntu | xenial | * |
The sensitive information may be valuable information on its own (such as a password), or it may be useful for launching other, more serious attacks. The error message may be created in different ways:
An attacker may use the contents of error messages to help launch another, more focused attack. For example, an attempt to exploit a path traversal weakness (CWE-22) might yield the full pathname of the installed application. In turn, this could be used to select the proper number of “..” sequences to navigate to the targeted file. An attack using SQL injection (CWE-89) might not initially succeed, but an error message could reveal the malformed query, which would expose query logic and possibly even passwords or other sensitive information used within the query.