Loading vulnerability…
CVE-2015-3337 is a directory traversal vulnerability in Elasticsearch affecting versions before 1.4.5 and 1.5.x before 1.5.2. The flaw is exposed through the site plugin functionality and allows a remote attacker to traverse outside the intended plugin content directory and read arbitrary files from the underlying filesystem. The issue is distinct from the separate Elasticsearch Snapshot API traversal flaw tracked as CVE-2015-5531 because it uses the site plugins attack surface rather than snapshot handling. Exploitation requires that a site plugin be enabled on the target Elasticsearch instance.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a Python proof-of-concept exploit for CVE-2015-3337, a directory traversal vulnerability in Elasticsearch (<= 1.6) with the Head plugin enabled. The exploit (CVE-2015-3337.py) allows an attacker to read arbitrary files from the server's filesystem by sending crafted HTTP GET requests to the vulnerable endpoint. The script is interactive, prompting the user to set the target URL and specify file paths to read. The README provides usage instructions and example output, demonstrating successful file reads (e.g., /etc/passwd, /etc/hosts). The repository is structured simply, with one exploit script and a README, and is intended for testing or demonstrating the vulnerability.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.