CVE-2012-4457 json
OpenStack Keystone Token authorization for a user in a disabled tenant is allowed
published 2012-10-09 14 y ago modified 2026-07-07 4 mo ago also GHSA-x8h4-xf47-pqc3 , PYSEC-2026-834 , EUVD-2022-5747
- cvss
- 4.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
OpenStack Keystone Essex before 2012.1.2 and Folsom before folsom-3 does not properly handle authorization tokens for disabled tenants, which allows remote authenticated users to access the tenant's resources by requesting a token for the tenant.
Patch / fix
- pypi keystone 8.0.0a0
- openstack keystone 2012.1.2
- keystone Debian 14, Debian 13, Debian 12 2012.1.1-9
debian advisories DEBIAN-CVE-2012-4457
- openstack-keystone openstack 1 2012.1.2-4.el6
- python-keystone openstack 1 2012.1.2-4.el6
- python-keystone-auth-token openstack 1 2012.1.2-4.el6
red hat advisories RHSA-2012:1378
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-4457 updated cvss 4.0
2012.1.1: fails to raise Unauthorized user error for disabled tenant
-
Red Hat RHOS Essex Release python-keystone 2012.1.2-4.el6, openstack-keystone 2012.1.2-4.el6, python-keystone-auth-token 2012.1.2-4.el6fixed: vendor fix RHSA-2012:1378
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.29% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | keystone | <8.0.0a0 |
8.0.0a0 |
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
github.com
/openstack/keystone/commit/5373601bbdda10f879c08af1698852142b75f8d5
web, third-party-advisory
-
github.com
/openstack/keystone/commit/4ebfdfaf23c6da8e3c182bf3ec2cb2b7132ef685
web, third-party-advisory
-
secunia.com
/advisories/50665
third-party-advisory, web
-
bugzilla.redhat.com
/show_bug.cgi?id=861180
web, issue-tracking, third-party-advisory
-
lists.launchpad.net
/openstack/msg17035.html
mailing-list, web, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/78947
vdb-entry, web, third-party-advisory
-
openwall.com
/lists/oss-security/2012/09/28/6
mailing-list, web, third-party-advisory
-
securityfocus.com
/bid/55716
vdb-entry, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2012-4457
advisory
-
github.com
/openstack/keystone
package
-
pypi.org
/project/keystone
package
-
github.com
/advisories/GHSA-x8h4-xf47-pqc3
advisory
Sources
- CVE List CVE-2012-4457
- GitHub Advisory GHSA-x8h4-xf47-pqc3
- NVD CVE-2012-4457
- OSV PYSEC-2026-834
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.