{"answers":{"affected":"3 open source packages ship an affected version, including apache-libcloud. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6480 exists.","fix":"Upgrade apache-libcloud to 0.13.3 or later.","what":"CVE-2013-6480 is a low-severity vulnerability in n/a, published on 7 Jan 2014. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-6480 and fix it if it is affected.\n\nWhat it is: CVE-2013-6480 is a low-severity vulnerability in n/a, published on 7 Jan 2014. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6480 exists.\n\nAffected packages and fixed versions:\n- apache-libcloud (PyPI): affected from 0.12.3; fixed in 0.13.3\n- apache-libcloud (PyPI): affected from 0.12.3; fixed in 0.13.3\n- apache-libcloud (PyPI): affected from 0.12.3; fixed in 0.13.3\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-6480/ (Markdown: https://insights.sbomify.com/CVE-2013-6480/index.md)","id":"CVE-2013-6480","markdown":"https://insights.sbomify.com/CVE-2013-6480/index.md","name":"CVE-2013-6480","record":{"aliases":["GHSA-g892-9h8m-r69r","PYSEC-2014-97"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python cloud library","requires_auth":"none","summary":"Local attackers can recover sensitive data from destroyed DigitalOcean VMs because Libcloud fails to scrub data during destruction.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"libcloud","vendor":"apache"}],"cvss":{"score":2.1,"severity":"low","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Libcloud 0.12.3 through 0.13.2 does not set the scrub_data parameter for the destroy DigitalOcean API, which allows local users to obtain sensitive information by leveraging a new VM.","ecosystems":["PyPI"],"exploits":{"exploitdb":1,"first_seen":"2014-01-01","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2014-01-01","kind":"exploitdb","ref":"38937","stars":null,"title":"Apache Libcloud Digital Ocean API - Local Information Disclosure"}],"tier":"weaponised"},"has_fix":true,"headline":"Libcloud does not properly scrub data when destroying a DigitalOcean node","id":"CVE-2013-6480","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2013"},"n_packages":3,"n_references":6,"next":{"headline":"libpurple/protocols/yahoo/libymsg.c in Pidgin before 2.10.8 allows remote attackers to cause a denial of service (crash) via a Yahoo!","id":"CVE-2013-6481"},"packages":[{"ecosystem":"PyPI","fixed":["0.13.3"],"introduced":["0.12.3"],"last_affected":[],"package":"apache-libcloud","purl":null,"source":"GHSA-g892-9h8m-r69r"},{"ecosystem":"PyPI","fixed":["0.13.3"],"introduced":["0.12.3"],"last_affected":[],"package":"apache-libcloud","purl":"pkg:pypi/apache-libcloud","source":"GHSA-g892-9h8m-r69r"},{"ecosystem":"PyPI","fixed":["0.13.3"],"introduced":["0.12.3"],"last_affected":[],"package":"apache-libcloud","purl":"pkg:pypi/apache-libcloud","source":"PYSEC-2014-97"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2013-6479"},"products":["n/a"],"published":"2014-01-07","related":[{"cvss_score":5.9,"headline":"Apache Libcloud vulnerable to certificate impersonation","id":"CVE-2012-3446","kev_date_added":null,"published":"2012-11-04"},{"cvss_score":4.3,"headline":"Apache Libcloud does not verify SSL certificates for HTTPS connections","id":"CVE-2010-4340","kev_date_added":null,"published":"2011-09-11"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Local attackers can recover sensitive data from destroyed DigitalOcean VMs because Libcloud fails to scrub data during destruction.","url":"https://insights.sbomify.com/CVE-2013-6480/"}