How severe is CVE-2014-3517?

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

Which packages are affected by CVE-2014-3517?

CVE-2014-3517 affects the following packages: nova (PyPI), nova (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2014-3517?

Update nova to 2013.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3517 is resolved across your whole dependency graph.

How do I detect CVE-2014-3517 in my PyPI dependencies?

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

How do I mitigate CVE-2014-3517 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-2014-3517 actively exploited in the wild?

No public exploit code has been indexed for CVE-2014-3517 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2014-3517?

CVE-2014-3517 has an EPSS (Exploit Prediction Scoring System) score of 2.0%, placing it in the 80th 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-2014-3517?

CVE-2014-3517 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-2014-3517 published, and has it been updated?

CVE-2014-3517 was published on August 7, 2014 and was last updated on July 7, 2026. 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-2014-3517 — nova

CVE-2014-3517 is a Information Exposure vulnerability in nova. A fix is available for nova — see the affected versions and patch details below.

OpenStack Compute (Nova) Exposure of Sensitive Information to an Unauthorized Actor vulnerability

Also known asGHSA-xjmj-p278-4jp5PYSEC-2026-884

Published

Aug 7, 2014

Updated

Jul 7, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs80th percentile — riskier than 80% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

🐍nova🐍nova

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

api/metadata/handler.py in OpenStack Compute (Nova) before 2013.2.4, 2014.x before 2014.1.2, and Juno before Juno-2, when proxying metadata requests through Neutron, makes it easier for remote attackers to guess instance ID signatures via a brute-force attack that relies on timing differences in responses to instance metadata requests.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`nova`	all versions	2013.2.4`pip install --upgrade 'nova==2013.2.4'`
🐍PyPI	`nova`	≥ 2014.0.0&&< 2014.1.2	2014.1.2`pip install --upgrade 'nova==2014.1.2'`

Affected Products

1 product · 3 configurations

Application

novaopenstack

≥ 2014.1 && ≤ 2013.2.4

1 version

2014.2.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nova, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update nova to 2013.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3517 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
OpenStack 4 for RHEL 6	`openstack-nova-0:2013.2.3-12.el6ost`	RHSA-2014:1084
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 7	`openstack-nova-0:2014.1.1-4.el7ost`	RHSA-2014:0940

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-3517 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works