Loading vulnerability…
CVE-2018-9159 is a path-traversal flaw in the Spark Java web framework before version 2.7.2. Spark's static-file handling permitted multiple representations of absolute or relative pathnames, including file-scheme URIs and directory-traversal sequences, to bypass intended static-resource path restrictions and disclose unintended files. This issue affects Spark Framework and is unrelated to Ignite Realtime Spark.
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.
No valid public exploits. Mallory filtered out 3 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Spark flaw in which absolute and relative pathnames can cause unintended disclosure of static files.
A Spark Framework vulnerability mentioned as a related example of vulnerable path-cleaning logic.
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.