Skip to content
Noroxi
CVE-2013-7130· NVD / CVE Program· CNA mitre

The i_create_images_and_backing (aka create_images_and_backing) method in libvirt driver in OpenStack Compute (Nova) Grizzly, Havana, and Ic

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.

HighCVSS 7.1 · v2.0—No exploit Fix available
Published
Feb 6, 2014
Updated
Jun 16, 2026
EPSS
2.4% · 84th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

29

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.4%

Affected systems

VendorProduct
openstackcompute
openstackgrizzly
openstackhavana
openstackicehouse

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • openstack compute2012.2
  • openstack compute2013.1
  • openstack compute2013.1.1
  • openstack compute2013.1.2
  • openstack compute2013.1.3
  • openstack grizzlyall versions
  • openstack havanaall versions
  • openstack icehouseall versions

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12novabefore 2013.2.22013.2.2
PyPInovabefore 12.0.0a012.0.0a0
Red Hat:openstack:3::el6openstack-novabefore 0:2013.1.5-2.el6ost0:2013.1.5-2.el6ost
Red Hat:openstack:3::el6openstack-nova-apibefore 0:2013.1.5-2.el6ost0:2013.1.5-2.el6ost
Red Hat:openstack:3::el6openstack-nova-cellsbefore 0:2013.1.5-2.el6ost0:2013.1.5-2.el6ost
Red Hat:openstack:3::el6openstack-nova-certbefore 0:2013.1.5-2.el6ost0:2013.1.5-2.el6ost
Red Hat:openstack:3::el6openstack-nova-commonbefore 0:2013.1.5-2.el6ost0:2013.1.5-2.el6ost
Red Hat:openstack:3::el6openstack-nova-computebefore 0:2013.1.5-2.el6ost0:2013.1.5-2.el6ost
Red Hat:openstack:3::el6openstack-nova-conductorbefore 0:2013.1.5-2.el6ost0:2013.1.5-2.el6ost
Red Hat:openstack:3::el6openstack-nova-consolebefore 0:2013.1.5-2.el6ost0:2013.1.5-2.el6ost
Red Hat:openstack:3::el6openstack-nova-docbefore 0:2013.1.5-2.el6ost0:2013.1.5-2.el6ost
Red Hat:openstack:3::el6openstack-nova-networkbefore 0:2013.1.5-2.el6ost0:2013.1.5-2.el6ost
Red Hat:openstack:3::el6openstack-nova-objectstorebefore 0:2013.1.5-2.el6ost0:2013.1.5-2.el6ost
Red Hat:openstack:3::el6openstack-nova-schedulerbefore 0:2013.1.5-2.el6ost0:2013.1.5-2.el6ost
Red Hat:openstack:3::el6python-novabefore 0:2013.1.5-2.el6ost0:2013.1.5-2.el6ost
Red Hat:openstack:4::el6openstack-novabefore 0:2013.2.2-2.el6ost0:2013.2.2-2.el6ost
Red Hat:openstack:4::el6openstack-nova-apibefore 0:2013.2.2-2.el6ost0:2013.2.2-2.el6ost
Red Hat:openstack:4::el6openstack-nova-cellsbefore 0:2013.2.2-2.el6ost0:2013.2.2-2.el6ost
Red Hat:openstack:4::el6openstack-nova-certbefore 0:2013.2.2-2.el6ost0:2013.2.2-2.el6ost
Red Hat:openstack:4::el6openstack-nova-commonbefore 0:2013.2.2-2.el6ost0:2013.2.2-2.el6ost
Red Hat:openstack:4::el6openstack-nova-computebefore 0:2013.2.2-2.el6ost0:2013.2.2-2.el6ost
Red Hat:openstack:4::el6openstack-nova-conductorbefore 0:2013.2.2-2.el6ost0:2013.2.2-2.el6ost
Red Hat:openstack:4::el6openstack-nova-consolebefore 0:2013.2.2-2.el6ost0:2013.2.2-2.el6ost
Red Hat:openstack:4::el6openstack-nova-docbefore 0:2013.2.2-2.el6ost0:2013.2.2-2.el6ost

+5

Other highest-scoring records for the same primary product.

  • CVE-2014-0167The Nova EC2 API security group implementation in OpenStack Compute (Nova) 2013.1 before 2013.2.4 and icehouse before icehouse-rc2 does not
    24Monitor
  • CVE-2013-2255HTTPSConnections in OpenStack Keystone 2013, OpenStack Compute 2013.1, and possibly other OpenStack components, fail to validate server-side
    23Monitor
  • CVE-2015-2687OpenStack Compute (nova) Icehouse, Juno and Havana when live migration fails allows local users to access VM volumes that they would normall
    18Monitor
  • CVE-2012-2654The (1) EC2 and (2) OS APIs in OpenStack Compute (Nova) Folsom (2012.2), Essex (2012.1), and Diablo (2011.3) do not properly check the proto
    18Monitor
  • CVE-2013-4185Algorithmic complexity vulnerability in OpenStack Compute (Nova) before 2013.1.3 and Havana before havana-3 does not properly handle network
    17Monitor
  • CVE-2012-3371The Nova scheduler in OpenStack Compute (Nova) Folsom (2012.2) and Essex (2012.1), when DifferentHostFilter or SameHostFilter is enabled, al
    15Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:nova2013.2.2 · Debian:12Package registry (OSV)
PyPI:nova12.0.0a0Package registry (OSV)
red hat:openstack-nova0:2013.2.2-2.el6ost · Red Hat:openstack:4::el6Package registry (OSV)
red hat:openstack-nova-api0:2013.2.2-2.el6ost · Red Hat:openstack:4::el6Package registry (OSV)
red hat:openstack-nova-cells0:2013.2.2-2.el6ost · Red Hat:openstack:4::el6Package registry (OSV)
red hat:openstack-nova-cert0:2013.2.2-2.el6ost · Red Hat:openstack:4::el6Package registry (OSV)
red hat:openstack-nova-common0:2013.2.2-2.el6ost · Red Hat:openstack:4::el6Package registry (OSV)
red hat:openstack-nova-compute0:2013.2.2-2.el6ost · Red Hat:openstack:4::el6Package registry (OSV)
red hat:openstack-nova-conductor0:2013.2.2-2.el6ost · Red Hat:openstack:4::el6Package registry (OSV)
red hat:openstack-nova-console0:2013.2.2-2.el6ost · Red Hat:openstack:4::el6Package registry (OSV)
red hat:openstack-nova-doc0:2013.2.2-2.el6ost · Red Hat:openstack:4::el6Package registry (OSV)
red hat:openstack-nova-network0:2013.2.2-2.el6ost · Red Hat:openstack:4::el6Package registry (OSV)
red hat:openstack-nova-novncproxy0:2013.2.2-2.el6ost · Red Hat:openstack:4::el6Package registry (OSV)
red hat:openstack-nova-objectstore0:2013.2.2-2.el6ost · Red Hat:openstack:4::el6Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

    If successful

    Confidentiality
    C · data can be read
    Integrity
    none
    Availability
    none
    Attack complexity
    M
    Confidentiality impact
    C
    Integrity impact
    None
    Availability impact
    None

    CVSS vector

    AV:N/AC:M/Au:N/C:C/I:N/A:N

    nvd-primary

    Root cause

    The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

    A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

    Vulnerable

    json
    {  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

    Fixed

    json
    {  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

    Noroxi analysis

    No Noroxi analysis for this record yet

    We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

    We use this product, ask for help

    Change log

    1. Fix✗ → ✓

    For records you follow, these changes also arrive as notifications. →

    References

    All records