CVE-2013-5093 in the critical feed json
graphite-web is vulnerable to Remote Code Execution via renderLocalView function
published 13y ago modified 4mo ago also GHSA-m923-w2gj-v43g , PYSEC-2013-3 , EUVD-2013-0011
- cvss
- 9.0
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 38.8%
- EPSS 38.8% chance of exploitation in 30 days, percentile 98%
- public exploits
- 2
- Metasploit and Exploit-DB
Summary
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.
Patch / fix
- pypi graphite-web 0.9.11
- graphite-web Debian 14, Debian 13, Debian 12 0.9.12+debian-1
debian advisories DEBIAN-CVE-2013-5093
Is CVE-2013-5093 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-5093 updated cvss 6.8
graphite-web: remote code execution flaw due to pickle processing
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Timeline
- First public exploit (Metasploit exploit/unix/webapp/graphite_pickle_exec)
- Published
Exploit prediction
38.81% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/unix/webapp/graphite_pickle_exec Graphite Web Unsafe Pickle Handling metasploit exploit, excellent rank, 2013-08-20
- EDB-27752 Graphite Web - Unsafe Pickle Handling (Metasploit) remote, 2013-08-21
- github.com https://github.com/graphite-project/graphite-web/blob/master/docs/releases/0_9_11.rst referenced PoC, tagged "exploit" by a source, unverified
- ceriksen.com http://ceriksen.com/2013/08/20/graphite-remote-code-execution-vulnerability-advisory/ referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/61894 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 9.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | graphite-web | >=0.9.5, <0.9.11 |
0.9.11 |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
github.com
/graphite-project/graphite-web/blob/master/docs/releases/0_9_11.rst
web, exploit, patch
-
exploit-db.com
/exploits/27752
exploit, web
-
ceriksen.com
/2013/08/20/graphite-remote-code-execution-vulnerability-advisory/
exploit, advisory
-
securityfocus.com
/bid/61894
vdb-entry, exploit, web
-
github.com
/rapid7/metasploit-framework/blob/master/modules/exploits/unix/webapp/graphite_pickle_exec.rb
web, exploit
-
secunia.com
/advisories/54556
third-party-advisory, vendor-advisory, advisory
-
osvdb.org
/96436
vdb-entry, web
-
nvd.nist.gov
/vuln/detail/CVE-2013-5093
advisory
-
github.com
/graphite-project/graphite-web
package
-
github.com
/graphite-project/graphite-web/blob/d39d455622127e479d8c4e7760311e3883cfd086/docs/releases/0_9_11.rst
web
-
github.com
/pypa/advisory-database/tree/main/vulns/graphite-web/PYSEC-2013-3.yaml
web
-
web.archive.org
/web/20200228174538/http://www.securityfocus.com/bid/61894
web
-
ceriksen.com
/2013/08/20/graphite-remote-code-execution-vulnerability-advisory
web
-
github.com
/advisories/GHSA-m923-w2gj-v43g
advisory
Sources
- CVE List CVE-2013-5093
- GitHub Advisory GHSA-m923-w2gj-v43g
- NVD CVE-2013-5093
- OSV PYSEC-2013-3
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.