CVE-2012-0030 json
Nova 2011.3 and Essex, when using the OpenStack API, allows remote authenticated users to bypass access restrictions for tenants of other u…
published 2012-01-13 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-0070
- cvss
- 4.9
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
Nova 2011.3 and Essex, when using the OpenStack API, allows remote authenticated users to bypass access restrictions for tenants of other users via an OSAPI request with a modified project_id URI parameter.
Patch / fix
- nova Debian 14, Debian 13, Debian 12 2012.1~rc1-1
debian advisories DEBIAN-CVE-2012-0030
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-0030 updated cvss 6.5
openstack-nova: Tenant bypass by authenticated users using OpenStack API
-
Red Hat All currently supported Red Hat productsnot 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.69% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.9 | AV:N/AC:M/Au:S/C:N/I:P/A:P |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
- github.com /openstack/nova/commit/3d4ffb64f1e18117240c26809788528979e3bd15#diff-0
-
lists.launchpad.net
/openstack/msg06648.html
mailing-list, patch
-
ubuntu.com
/usn/USN-1326-1
vendor-advisory
-
secunia.com
/advisories/47543
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/72296
vdb-entry
-
securityfocus.com
/bid/51370
vdb-entry
Sources
- CVE List CVE-2012-0030
- NVD CVE-2012-0030
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.