CVE Vulnerabilities

CVE-2013-7130

Exposure of Sensitive Information to an Unauthorized Actor

Published: Feb 06, 2014 | Modified: Aug 29, 2017
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
7.1 HIGH
AV:N/AC:M/Au:N/C:C/I:N/A:N
RedHat/V2
3.5 MODERATE
AV:N/AC:M/Au:S/C:P/I:N/A:N
RedHat/V3
Ubuntu

The i_create_images_and_backing (aka create_images_and_backing) method in libvirt driver in OpenStack Compute (Nova) Grizzly, Havana, and Icehouse, when using KVM live block migration, does not properly create all expected files, which allows attackers to obtain snapshot root disk contents of other users via ephemeral storage.

Weakness

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Affected Software

Name Vendor Start Version End Version
Compute Openstack 2012.2 2012.2
Compute Openstack 2013.1 2013.1
Compute Openstack 2013.1.1 2013.1.1
Compute Openstack 2013.1.2 2013.1.2
Compute Openstack 2013.1.3 2013.1.3
Grizzly Openstack - -
Havana Openstack - -
Icehouse Openstack - -
OpenStack 3 for RHEL 6 RedHat openstack-nova-0:2013.1.5-2.el6ost *
OpenStack 4 for RHEL 6 RedHat openstack-nova-0:2013.2.2-2.el6ost *
Nova Ubuntu precise *
Nova Ubuntu quantal *
Nova Ubuntu raring *
Nova Ubuntu saucy *
Nova Ubuntu upstream *

Extended Description

There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:

Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:

Information exposures can occur in different ways:

It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.

Potential Mitigations

  • 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