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 products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Red Hat | OpenStack Folsom for RHEL 6 | — | — |
| Red Hat | Red Hat OpenStack Platform 16.2 | — | — |
| Red Hat | Red Hat OpenStack Platform 17.1 | — | — |
| Red Hat | Red Hat OpenStack Platform 18.0 | — | — |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| PyPI | nova | < 12.0.0a0 | 12.0.0a0 | GHSA-rwhr-h69g-8qmq |
| PyPI | nova | — | — | PYSEC-2012-42 |
References
- http://osvdb.org/88419
- http://rhn.redhat.com/errata/RHSA-2013-0208.html
- http://www.openwall.com/lists/oss-security/2012/12/11/5
- http://www.securityfocus.com/bid/56904
- http://www.ubuntu.com/usn/USN-1663-1
- RHSA-2013:0208 vendor-advisory
- https://access.redhat.com/security/cve/CVE-2012-5625 vdb-entry
- https://bugs.launchpad.net/nova/+bug/1070539
- https://bugzilla.redhat.com/show_bug.cgi?id=884293
- https://github.com/openstack/nova/commit/9d2ea970422591f8cdc394001be9a2deca499a5f
- https://github.com/openstack/nova/commit/a99a802e008eed18e39fc1d98170edc495cbd354
- https://launchpad.net/nova/folsom/2012.2.2