Skip to content
Fencer Intel
medium 4.3

CVE-2012-2654 json

OpenStack Compute (Nova) Improper Input Validation

published 2012-06-21 14 y ago modified 2026-06-16 4 mo ago also GHSA-46r8-9cj7-pw6g , PYSEC-2012-37 , EUVD-2012-0020

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

Summary

The (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 protocol when security groups are created and the network protocol is not specified entirely in lowercase, which allows remote attackers to bypass intended access restrictions.

Patch / fix

  • pypi nova 12.0.0a0
  • nova Debian 14, Debian 13, Debian 12 2012.1-6

debian advisories DEBIAN-CVE-2012-2654

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-2012-2654 updated cvss 2.1

OpenStack Nova security groups fail to be set correctly

  • Red Hat All currently supported Red Hat products
    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

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

Exploits and checks

  • github.com https://github.com/openstack/nova/commit/9f9e9da777161426a6f8cb4314b78e09beac2978 referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/openstack/nova/commit/ff06c7c885dc94ed7c828e8cdbb8b5d850a7e654 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected packages

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

Classification

Weakness
  • CWE-20 Improper Input Validation

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.