Skip to content
Fencer Intel
medium 6.5

CVE-2014-2573 json

OpenStack Nova VMWare driver leaks rescued images

published 2014-03-25 12 y ago modified 2026-06-17 4 mo ago also GHSA-jv34-xvjq-ppch , PYSEC-2014-113 , EUVD-2014-0037

cvss
6.5
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits
0
none known

Summary

The VMWare driver in OpenStack Compute (Nova) 2013.2 through 2013.2.2 does not properly put VMs into RESCUE status, which allows remote authenticated users to bypass the quota limit and cause a denial of service (resource consumption) by requesting the VM be put into rescue and then deleting the image.

Patch / fix

  • pypi nova 12.0.0a0
  • nova Debian 14, Debian 13, Debian 12 2014.1-9

debian advisories DEBIAN-CVE-2014-2573

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-2573 updated cvss 4.0

openstack-nova: Nova VMware driver leaks rescued images

  • Red Hat OpenStack Platform 3 openstack-nova Red Hat OpenStack Platform 4 openstack-nova
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux OpenStack Platform 5 (Icehouse) openstack-nova
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.70% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 2.3 AV:A/AC:M/Au:S/C:N/I:N/A:P
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
pypi nova
<12.0.0a0
12.0.0a0

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.