Skip to content
Fencer Intel
low 3.5

CVE-2013-4278 json

OpenStack Compute (Nova) Resource limit circumvention in Nova private flavors

published 13y ago modified 4mo ago also GHSA-43cm-73px-5v4m , PYSEC-2026-862 , EUVD-2022-2280

cvss
3.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits
0
none known

Summary

The "create an instance" API in OpenStack Compute (Nova) Folsom, Grizzly, and Havana does not properly enforce the os-flavor-access:is_public property, which allows remote authenticated users to boot arbitrary flavors by guessing the flavor id. NOTE: this issue is due to an incomplete fix for CVE-2013-2256.

Patch / fix

  • pypi nova 12.0.0a0
  • nova Debian 14, Debian 13, Debian 12 2013.1.3-1

debian advisories DEBIAN-CVE-2013-4278

Is CVE-2013-4278 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2013-4278 updated cvss 5.5

OpenStack: Nova private flavors resource limit circumvention incomplete fix for CVE-2013-2256

  • Red Hat OpenStack Platform 3 openstack-nova Red Hat OpenStack Platform 4 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

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

CVSS scores

assigned by version score vector
NVD 2.0 3.5 AV:N/AC:M/Au:S/C:P/I:N/A:N

Affected packages

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

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

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.