CVE-2021-28164GHSA-V7FF-8WCX-GMC5
In Eclipse Jetty 9.4.37.v20210219 to 9.4.38.v20210224, the default compliance mode allows requests with URIs that contain %2e or %2e%2e segm
- 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.4.39
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 on Exploit-DB, 1 Metasploit module, 2 proofs of concept on GitHub, 1 Nuclei template
Summary
In Eclipse Jetty 9.4.37.v20210219 to 9.4.38.v20210224, the default compliance mode allows requests with URIs that contain %2e or %2e%2e segments to access protected resources within the WEB-INF directory. For example a request to /context/%2e/WEB-INF/web.xml can retrieve the web.xml file. This can reveal sensitive information regarding the implementation of a web application.
Timeline
- CVE published
- Public exploit on Exploit-DB
EDB-50438
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- The Eclipse Foundation Eclipse Jetty
From 9.4.37.v20210219; through 9.4.38.v20210224
- org.eclipse.jetty:jetty-webappMaven
From 9.4.37 · fixed in 9.4.39
References 30
GitHub · eclipse/jetty.project
lists.apache.org
- thread.html/r780c3c210a05c5bf7b4671303f46afc3fe56758e92864e1a5f0590d0@<jira.kafka.apache.org>
- thread.html/r5b3693da7ecb8a75c0e930b4ca26a5f97aa0207d9dae4aa8cc65fe6b@<issues.ignite.apache.org>
- thread.html/rd7c8fb305a8637480dc943ba08424c8992dccad018cd1405eb2afe0e@<dev.ignite.apache.org>
- thread.html/r0841b06b48324cfc81325de3c05a92e53f997185f9d71ff47734d961@<issues.solr.apache.org>
- thread.html/r6ac9e263129328c0db9940d72b4a6062e703c58918dd34bd22cdf8dd@<issues.ignite.apache.org>
- thread.html/r4a66bfbf62281e31bc1345ebecbfd96f35199eecd77bfe4e903e906f@<issues.ignite.apache.org>
- thread.html/r4b1fef117bccc7f5fd4c45fd2cabc26838df823fe5ca94bc42a4fd46@<issues.ignite.apache.org>
- thread.html/r111f1ce28b133a8090ca4f809a1bdf18a777426fc058dc3a16c39c66@<issues.solr.apache.org>
- thread.html/r2ea2f0541121f17e470a0184843720046c59d4bde6d42bf5ca6fad81@<issues.solr.apache.org>
- thread.html/r9974f64723875052e02787b2a5eda689ac5247c71b827d455e5dc9a6@<issues.solr.apache.org>
- thread.html/rbc075a4ac85e7a8e47420b7383f16ffa0af3b792b8423584735f369f@<issues.solr.apache.org>
- thread.html/r7dd079fa0ac6f47ba1ad0af98d7d0276547b8a4e005f034fb1016951@<issues.zookeeper.apache.org>
- thread.html/r90e7b4c42a96d74c219e448bee6a329ab0cd3205c44b63471d96c3ab@<issues.zookeeper.apache.org>
- thread.html/r763840320a80e515331cbc1e613fa93f25faf62e991974171a325c82@<dev.zookeeper.apache.org>
- thread.html/r2a3ea27cca2ac7352d392b023b72e824387bc9ff16ba245ec663bdc6@<issues.zookeeper.apache.org>
- thread.html/r8e6c116628c1277c3cf132012a66c46a0863fa2a3037c0707d4640d4@<issues.zookeeper.apache.org>
- thread.html/rd0471252aeb3384c3cfa6d131374646d4641b80dd313e7b476c47a9c@<issues.solr.apache.org>
- thread.html/rcea249eb7a0d243f21696e4985de33f3780399bf7b31ea1f6d489b8b@<issues.zookeeper.apache.org>
- thread.html/r3c55b0baa4dc38958ae147b2f216e212605f1071297f845e14477d36@<issues.zookeeper.apache.org>