{"answers":{"affected":"3 open source packages ship an affected version, including graphite-web. It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-5942 in the wild and no public exploit code.","fix":"Upgrade graphite-web to 0.9.11 or later.","what":"CVE-2013-5942 is a medium-severity unsafe deserialization vulnerability in n/a, published on 27 Sep 2013. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-5942 and fix it if it is affected.\n\nWhat it is: CVE-2013-5942 is a medium-severity unsafe deserialization vulnerability in n/a, published on 27 Sep 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2013-5942 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- graphite-web (PyPI): affected from 0.9.5; fixed in 0.9.11\n- graphite-web (PyPI): affected from 0.9.5; fixed in 0.9.11\n- graphite-web (PyPI): affected from 0.9.5; fixed in 0.9.11\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2013-5942/ (Markdown: https://insights.sbomify.com/CVE-2013-5942/index.md)","id":"CVE-2013-5942","markdown":"https://insights.sbomify.com/CVE-2013-5942/index.md","name":"CVE-2013-5942","record":{"aliases":["DEBIAN-CVE-2013-5942","GHSA-ch3j-w953-hfcm","PYSEC-2013-34"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Graphite monitoring server","requires_auth":"none","summary":"Remote attackers can execute arbitrary code on Graphite servers by sending crafted serialized objects due to unsafe pickle usage.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"graphite","vendor":"graphite_project"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"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, related to (1) remote_storage.py, (2) storage.py, (3) render/datalib.py, and (4) whitelist/views.py, a different vulnerability than CVE-2013-5093.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"graphite-web is vulnerable to Remote Code Execution","id":"CVE-2013-5942","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"deserialization","year":"2013"},"n_packages":3,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2013-5943"},"packages":[{"ecosystem":"PyPI","fixed":["0.9.11"],"introduced":["0.9.5"],"last_affected":[],"package":"graphite-web","purl":null,"source":"GHSA-ch3j-w953-hfcm"},{"ecosystem":"PyPI","fixed":["0.9.11"],"introduced":["0.9.5"],"last_affected":[],"package":"graphite-web","purl":"pkg:pypi/graphite-web","source":"GHSA-ch3j-w953-hfcm"},{"ecosystem":"PyPI","fixed":["0.9.11"],"introduced":["0.9.5"],"last_affected":[],"package":"graphite-web","purl":"pkg:pypi/graphite-web","source":"PYSEC-2013-34"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2013-5939"},"products":["n/a"],"published":"2013-09-27","related":[{"cvss_score":7.5,"headline":"graphite.composer.views.send_email vulnerable to SSRF","id":"CVE-2017-18638","kev_date_added":null,"published":"2019-10-11"},{"cvss_score":6.8,"headline":"graphite-web is vulnerable to Remote Code Execution via renderLocalView function","id":"CVE-2013-5093","kev_date_added":null,"published":"2013-09-27"},{"cvss_score":4.3,"headline":"Cross-site scripting in n/a","id":"CVE-2013-5943","kev_date_added":null,"published":"2013-09-27"},{"cvss_score":3.5,"headline":"Graphite Web Cookie cross site scripting","id":"CVE-2022-4728","kev_date_added":null,"published":"2022-12-24"},{"cvss_score":3.5,"headline":"Graphite Web Template Name cross site scripting","id":"CVE-2022-4729","kev_date_added":null,"published":"2022-12-24"},{"cvss_score":3.5,"headline":"Graphite Web Absolute Time Range cross site scripting","id":"CVE-2022-4730","kev_date_added":null,"published":"2022-12-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code on Graphite servers by sending crafted serialized objects due to unsafe pickle usage.","url":"https://insights.sbomify.com/CVE-2013-5942/"}