GHSA-xjmj-p278-4jp5 CVE-2014-3517 PYSEC-2026-884

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

Medium PyPI

Severity: Medium; The publisher's own rating, not a CVSS score
Exploit chance (EPSS): 1.95%; Chance of exploitation in the next 30 days. Higher than 80.26% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix: 2013.2.4; Upgrade nova to this version or later

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 versions

PyPI

Package	Vulnerable	Fixed in
nova	`< 2013.2.4`	`2013.2.4`
nova	`>= 2014.0.0, < 2014.1.2`	`2014.1.2`
nova	`< 2013.2.4` `>= 2014.0.0, < 2014.1.2`	`2013.2.4` `2014.1.2`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

nova PyPI → `2013.2.4`

pip

pip install --upgrade "nova>=2013.2.4"

poetry

poetry add "nova>=2013.2.4"

uv

uv add "nova>=2013.2.4"

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it

Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Advisories

Packages

Timeline

May 14, 2022 Published
Sep 10, 2026 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-mfg3-p6m3-gjgr OpenStack Nova: Nova scheduler hint injection bypasses Placement resource claims and scheduling constraints	High	Also affects nova
GHSA-m4f3-qp2w-gwh6 OpenStack Nova calls qemu-img without format restrictions for resize	High	Also affects nova
GHSA-rm86-h44c-2r2m OpenStack Nova vulnerable to unauthorized access to potentially sensitive data	Medium	Also affects nova
GHSA-r4v4-w9pv-6fph OpenStack Cinder, Glance, and Nova vulnerable to arbitrary file access	Medium	Also affects nova
GHSA-7h75-hwxx-qpgc OpenStack Cinder, glance, and Nova vulnerable to Path Traversal	Medium	Also affects nova
GHSA-v725-c588-h936 OpenStack Nova Changing vnic_type breaks compute service restart	Low	Also affects nova
GHSA-22jm-4hxw-35jf OpenStack Nova can leak consoleauth token into log files	Low	Also affects nova
GHSA-43cm-73px-5v4m OpenStack Compute (Nova) Resource limit circumvention in Nova private flavors	Low	Also affects nova

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor