jetty: full server path revealed when using the default Error Handling
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| The Eclipse Foundation | Eclipse Jetty | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Fuse 7.6.0 | |||
| cpe:/a:redhat:jboss_fuse:7 | RHSA-2020:0983 | 2020-03-26T00:00:00Z | |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-2661-1 | jetty9 security update |
EUVD |
EUVD-2018-0567 | 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. |
Github GHSA |
GHSA-9rgv-h7x4-qw8g | Eclipse Jetty Server generates error message containing sensitive information |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: 4.2% (4.235% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|