CVE-2012-5625 — Openstack nova: information leak in libvirt lvm-backed instances
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).
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 2% (30-day exploitation probability)+12
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — www.ubuntu.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Pip Nova: fixed in version 12.0.0a0 — github.com (GitHub Security Advisories)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (OpenStack Folsom, OpenStack Grizzly, Red Hat OpenStack Folsom for RHEL 6…).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| OpenStack | Folsom | version 2012.2 | Vulnerable | NIST National Vulnerability Database |
| OpenStack | Grizzly | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Red Hat | OpenStack Folsom for RHEL 6 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Pip | Nova | < 12.0.0a0 | Vulnerable | GitHub Security Advisories |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.5 | CVSS 3.1 | Medium | 2.0 | 4.0 | secalert@redhat.com via NIST National Vulnerability Database |
| 6.5 | CVSS 3.1 | Medium | — | — | redhat via CVE Program (cve.org) e CISA ADP |
| 4.3 | CVSS 2.0 | Medium | 8.6 | 2.9 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N (score shown at the top: secalert@redhat.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · pip/nova
- Affected products added · red hat/openstack folsom for rhel 6
- Record published
- Fix documented
- Affected products added · openstack/folsom, openstack/grizzly
- CVSS changed · 6.5
- Source status changed · → Modified
- Record created in this database
- 2012
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 30, 2026 – Oct 30, 2026
- 1× Official description updated · Oct 30, 2026 – Oct 30, 2026
References
16 on the record
- github.com/openstack/nova/commit/a99a802e008eed18e39fc1d98170edc495cbd354
- www.ubuntu.com/usn/USN-1663-1
- github.com/openstack/nova/commit/9d2ea970422591f8cdc394001be9a2deca499a5f
- github.com/pypa/advisory-database/tree/main/vulns/nova/PYSEC-2012-41.yaml
- bugs.launchpad.net/nova/+bug/1070539
- www.openwall.com/lists/oss-security/2012/12/11/5
- osvdb.org/88419
- access.redhat.com/errata/RHSA-2013:0208
- github.com/advisories/GHSA-rwhr-h69g-8qmq
- nvd.nist.gov/vuln/detail/CVE-2012-5625
- bugzilla.redhat.com/show_bug.cgi
- rhn.redhat.com/errata/RHSA-2013-0208.html
- github.com/pypa/advisory-database/tree/main/vulns/nova/PYSEC-2012-42.yaml
- www.securityfocus.com/bid/56904
- access.redhat.com/security/cve/CVE-2012-5625
- launchpad.net/nova/folsom/2012.2.2
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-46448 OpenStack Nova: Nova scheduler hint injection bypasses Placement resource claims and scheduling constraints Jun 16, 2026
- Medium CVE-2013-1815 Packstack: red hat openstack: packstack: unauthorized system modification via insecure answer file creation Apr 10, 2013
- Medium CVE-2013-1840 Openstack glance: swift: s3: openstack glance: information disclosure of backend credentials via cached image request Mar 22, 2013
- High CVE-2013-0261 Packstack: packstack: arbitrary file overwrite via symlink attack Mar 8, 2013
- Medium CVE-2013-0266 manifests/base.pp in the puppetlabs-cinder module, as used in PackStack, uses world-readable... Mar 8, 2013
- Medium CVE-2012-5571 Openstack keystone: openstack keystone: authorization bypass via improper ec2 token handling Dec 17, 2012
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2012-5625 is "Openstack nova: information leak in libvirt lvm-backed instances", rated Medium. It affects Folsom (OpenStack); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. EPSS 2.02% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.