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).
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2012-5625US | medium4.3 | — | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- http://rhn.redhat.com/errata/RHSA-2013-0208.htmlWEB
- http://www.openwall.com/lists/oss-security/2012/12/11/5WEB
- http://www.ubuntu.com/usn/USN-1663-1WEB
- https://bugs.launchpad.net/nova/+bug/1070539WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=884293WEB
- https://github.com/openstack/novaPACKAGE
- https://github.com/openstack/nova/commit/9d2ea970422591f8cdc394001be9a2deca499a5fWEB
- https://github.com/openstack/nova/commit/a99a802e008eed18e39fc1d98170edc495cbd354WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan