Installation information leak in Eclipse Jetty
The Eclipse Foundation Eclipse Jetty
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.eclipse.jetty:jetty-server Maven |
|
|
The Eclipse Foundation Eclipse Jetty
| Product | Affected | Fixed in |
|---|---|---|
| org.eclipse.jetty:jetty-server Maven |
|
|
In Eclipse Jetty version 7.x, 8.x, 9.2.27 and older, 9.3.26 and older, and 9.4.16 and older, the server running on any OS and Jetty version combination will reveal the configured fully qualified directory base resource location on the output of the 404 error for not finding a Context that matches the requested path. The default server behavior on jetty-distribution and jetty-home will include at the end of the Handler tree a DefaultHandler, which is responsible for reporting this 404 error, it presents the various configured contexts as HTML for users to click through to. This produced HTML includes output that contains the configured fully qualified directory base resource location for each context.
From the CVE record · eclipse
Eclipse Jetty's DefaultHandler can include configured, fully qualified directory base resource locations in an HTML 404 response. An attacker who requests a path that matches no configured context can see those locations when the server uses the described default handler behavior.
Operators using Maven org.eclipse.jetty:jetty-server versions >=7.0.0 and <9.2.28.v20190418, >=9.3.0 and <9.3.27.v20190418, or >=9.4.0 and <9.4.17.v20190418 should check their deployments.