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
- 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.2.28.v20190418, 9.3.27.v20190418, 9.4.17.v20190418
- 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 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.
Timeline
- CVE published
- Record last updated
Affected versions
- The Eclipse Foundation Eclipse Jetty
through 9.2.27; through 9.3.26; through 9.4.16
- org.eclipse.jetty:jetty-serverMaven
From 7.0.0 · fixed in 9.2.28.v20190418
- org.eclipse.jetty:jetty-serverMaven
From 9.3.0 · fixed in 9.3.27.v20190418
- org.eclipse.jetty:jetty-serverMaven
From 9.4.0 · fixed in 9.4.17.v20190418
References 18
lists.apache.org
- thread.html/ac51944aef91dd5006b8510b0bef337adaccfe962fb90e7af9c22db4@<issues.activemq.apache.org>
- thread.html/053d9ce4d579b02203db18545fee5e33f35f2932885459b74d1e4272@<issues.activemq.apache.org>
- thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@<dev.drill.apache.org>
- thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@<issues.drill.apache.org>
- thread.html/bcce5a9c532b386c68dab2f6b3ce8b0cc9b950ec551766e76391caa3@<commits.nifi.apache.org>
- thread.html/rca37935d661f4689cb4119f1b3b224413b22be161b678e6e6ce0c69b@<commits.nifi.apache.org>