CVE-2013-5093 graphite project graphite: Code Injection
graphite project graphite: no CVSS score yet. EPSS 39% estimated probability of exploitation activity in the next 30 days. Fixed in graphite-web 0.9.11.
On this page
The renderLocalView function in render/views.py in graphite-web in Graphite 0.9.5 through 0.9.10 uses the pickle Python module unsafely, which allows remote attackers to execute arbitrary code via a crafted serialized object.
- EPSS
- 39% (unchanged from 39% a week ago; 39% 30 days ago) estimated probability of exploitation activity in the next 30 days; 99th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-94 Improper Control of Generation of Code (Code Injection)
- OWASP Top 10
- A05:2025 Injection
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Fix and patched versions
graphite-web(PyPI): fixed in 0.9.11- Debian: fixed package versions per release
- Patch: https://github.com/graphite-project/graphite-web/blob/master/docs/releases/0_9_11.rst
- Vendor advisory: http://secunia.com/advisories/54556
Ask an AI about this CVE
Show the prompt
Explain CVE-2013-5093 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2013-5093?via=ask-ai-copy and https://cve.bz/cve/CVE-2013-5093?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2013-5093 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| graphite_project:graphite | 0.9.5 |
| graphite_project:graphite | 0.9.6 |
| graphite_project:graphite | 0.9.7 |
| graphite_project:graphite | 0.9.8 |
| graphite_project:graphite | 0.9.9 |
| graphite_project:graphite | 0.9.10 |
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-m923-w2gj-v43g | PyPI | graphite-web | >=0.9.5 <0.9.11 | 0.9.11 |
| PYSEC-2013-3 | PyPI | graphite-web | >=0.9.5 <0.9.11 | 0.9.11 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | graphite-web | 0.9.12+debian-1 | DEBIAN-CVE-2013-5093 |
From the distributions' data via OSV.dev: the Debian Security Tracker. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.
Public exploits
- Exploit-DB Graphite Web - Unsafe Pickle Handling (Metasploit)
- Metasploit Graphite Web Unsafe Pickle Handling
Attack patterns (CAPEC)
- CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
- CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
- CAPEC-242 Code Injection Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.
References
- https://github.com/graphite-project/graphite-web/blob/master/docs/releases/0_9_11.rst
- http://secunia.com/advisories/54556
- http://ceriksen.com/2013/08/20/graphite-remote-code-execution-vulnerability-advisory/
- http://www.exploit-db.com/exploits/27752
- http://www.osvdb.org/96436
- http://www.securityfocus.com/bid/61894
- https://github.com/rapid7/metasploit-framework/blob/master/modules/exploits/unix/webapp/graphite_pickle_exec.rb