Loading vulnerability…
Superset versions prior to 0.23 used Python's pickle library with an unsafe load method to deserialize data. This allows attackers to supply maliciously crafted pickle data, which can result in arbitrary code execution on the server running Superset. The vulnerability exists because pickle's load method executes arbitrary code during deserialization if the input is not properly sanitized.
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 exploit (exploit.py) targeting Apache Superset instances vulnerable to CVE-2018-8021, a remote code execution flaw due to unsafe deserialization with Python's pickle library. The exploit requires valid credentials for a Superset user with dashboard import privileges. It crafts a malicious pickle file that, when uploaded via the /superset/import_dashboards endpoint, executes a shell command on the server to establish a reverse shell back to the attacker's machine using netcat and a named pipe. The repository includes a README with usage instructions, references to the CVE and original PoC, and a single exploit script. The main attack vector is network-based, exploiting HTTP endpoints exposed by Superset. The exploit is operational, providing a working reverse shell payload, but requires attacker-supplied credentials and network access to the target Superset instance.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.