Loading vulnerability…
The renderLocalView function in render/views.py in Graphite-web versions 0.9.5 through 0.9.10 unsafely deserializes user-supplied data using Python's pickle module. This allows remote attackers to supply crafted serialized objects that, when deserialized, can result in arbitrary code execution on the server.
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.
This repository contains a single Metasploit module (graphite_pickle_exec.rb) that exploits a remote code execution vulnerability (CVE-2013-5093) in Graphite Web versions 0.9.5 through 0.9.10. The exploit leverages unsafe handling of Python pickle objects in the rendering code, allowing an attacker to send a specially crafted pickle payload via a POST request to the '/render/local' endpoint. The module first checks the version of the target application by sending a GET request to '/version/' and a POST to '/render/local', then delivers the payload if the target is vulnerable. The payload is customizable and allows arbitrary command execution on the target system. The exploit is weaponized, as it is part of the Metasploit framework and supports various command payloads. The only file in the repository is the Metasploit module itself, written in Ruby.
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.