CVE-2012-5625: Infoleak
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).
Other sources
Thierry Carrez (thierry) has released information
Title: Information leak in libvirt LVM-backed instances Reporter: Eric Windisch (Cloudscaling) Products: Nova Affects: Folsom, Grizzly
Description: Eric Windisch from Cloudscaling reported a vulnerability in libvirt LVM-backed instances. The physical volume content was not wiped out before being reallocated and passed to an instance, which may result in the disclosure of information from previously-allocated logical volumes. Only setups using libvirt and LVM-backed instances (libvirtimagestype=lvm) are affected.
This was originally reported by Eric Windisch from Cloudscaling
— Red Hat
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2012-5625?
CVE-2012-5625 is classified as a medium severity vulnerability that can lead to information disclosure.
How do I fix CVE-2012-5625?
To fix CVE-2012-5625, upgrade to OpenStack Compute (Nova) version 12.0.0a0 or later.
What are the affected versions for CVE-2012-5625?
CVE-2012-5625 affects OpenStack Compute (Nova) Folsom before version 2012.2.2 and Grizzly.
What type of attack can CVE-2012-5625 facilitate?
CVE-2012-5625 can allow an attacker to gain sensitive information by reading the physical volume content.
Which storage backend is vulnerable in CVE-2012-5625?
CVE-2012-5625 impacts instances using libvirt and LVM backed storage.