Skip to content

GHSA-rwhr-h69g-8qmq CVE-2012-5625 PYSEC-2012-41 PYSEC-2012-42

OpenStack Nova Information leak in libvirt LVM-backed instances

Medium PyPI
Severity
6.5 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
1.35%
Chance of exploitation in the next 30 days. Higher than 71.51% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix
12.0.0a0
Upgrade nova to this version or later

Description

OpenStack Compute (Nova) Folsom before 2012.2.2 and Grizzly, when using libvirt and LVM backed instances, does not properly clear physical volume (PV) content when reallocating for instances, which allows attackers to obtain sensitive information by reading the memory of the previous logical volume (LV).

Affected versions

PyPI

PackageVulnerableFixed in
nova
< 12.0.0a0
12.0.0a0
nova
all versions
No fix yet
nova See the source repository's commits No fix yet

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 → 12.0.0a0

pip
pip install --upgrade "nova>=12.0.0a0"
poetry
poetry add "nova>=12.0.0a0"
uv
uv add "nova>=12.0.0a0"

Severity breakdown

CVSS 3.1 6.5

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy 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