How severe is CVE-2013-6480?

No CVSS score has been assigned to CVE-2013-6480 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-6480?

CVE-2013-6480 affects the following packages: apache-libcloud (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2013-6480?

Update apache-libcloud to 0.13.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-6480 is resolved across your whole dependency graph.

How do I detect CVE-2013-6480 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for apache-libcloud, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-6480 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2013-6480 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2013-6480, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2013-6480?

CVE-2013-6480 has an EPSS (Exploit Prediction Scoring System) score of 2.1%, placing it in the 81th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-6480?

CVE-2013-6480 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-6480 published, and has it been updated?

CVE-2013-6480 was published on May 14, 2022 and was last updated on December 8, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2013-6480 — apache-libcloud

Fix: apache/libcloud@4449e16

CVE-2013-6480 is a Information Exposure vulnerability in apache-libcloud. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for apache-libcloud — see the affected versions and patch details below.

Libcloud does not properly scrub data when destroying a DigitalOcean node

Also known asPYSEC-2014-97

Published

May 14, 2022

Updated

Dec 8, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.1%probability of exploitation in next 30 days

Lower Risk-0.02%

Lower risk than most CVEs81th percentile — riskier than 81% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍apache-libcloud

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`apache-libcloud`	≥ 0.12.3&&< 0.13.3	0.13.3`pip install --upgrade 'apache-libcloud==0.13.3'`

Affected Products

1 product · 5 configurations

Application

libcloudapache

5 versions

0.12.30.12.40.13.00.13.10.13.2

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-38937locallinux✓ Verified

Apache Libcloud Digital Ocean API - Local Information Disclosure

by anonymous · Jan 1, 2014

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for apache-libcloud, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update apache-libcloud to 0.13.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-6480 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2013-6480 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works