CVE-2021-28164 is an information-disclosure vulnerability in Eclipse Jetty 9.4.37.v20210219 through 9.4.38.v20210224. Jetty's default URI-compliance mode accepts encoded current-directory and parent-directory path segments, such as %2e and %2e%2e. An attacker can use an ambiguous encoded path to bypass protection of resources beneath a deployed web application's WEB-INF directory, including deployment-descriptor content that can disclose application implementation details.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a single Metasploit auxiliary module targeting Jetty servers vulnerable to CVE-2021-34429 and CVE-2021-28164. The module exploits a path traversal vulnerability that allows remote attackers to access protected files within the WEB-INF directory by sending HTTP requests with specially encoded or ambiguous paths (e.g., /%u002e/WEB-INF/web.xml or /%2e/WEB-INF/web.xml). The module checks the Jetty version via the Server header, determines if the target is vulnerable, and, if so, retrieves the specified file (default: web.xml) from the server. The exploit is operational, providing file disclosure capabilities but not remote code execution. The code is written in Ruby and is designed to be used within the Metasploit framework.
This repository provides a proof-of-concept (PoC) exploit for CVE-2021-28164, a path traversal vulnerability in Eclipse Jetty 9.4.37. The main exploit is described in the '분석결과' file, which explains how to set up a vulnerable Jetty server using Docker and then exploit the vulnerability by sending a crafted HTTP request. The exploit uses a URL-encoded path ('%2e/') to bypass access controls and retrieve sensitive files such as '/WEB-INF/web.xml'. The repository contains a Jupyter notebook (AI_secHW_enhancingHW_try2.ipynb), but this is unrelated to the exploit and appears to be for machine learning experimentation. The README and '분석결과' files provide context and step-by-step instructions for reproducing the exploit. No weaponized or automated exploit code is present; the exploit is executed manually via a curl command. The main attack vector is network-based, targeting a web server endpoint.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Jetty path-handling flaw in which ambiguous paths can provide access to WEB-INF resources.
A Jetty path-handling vulnerability that permits ambiguous paths to access the protected WEB-INF directory.
Jetty ambiguous-path vulnerability that permits access to WEB-INF resources.
Jetty path-handling vulnerability allowing ambiguous paths to access WEB-INF resources.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.