CVE-2012-4413 json
OpenStack Keystone does not invalidate existing tokens when granting or revoking roles
published 2012-09-18 14 y ago modified 2026-09-10 1 mo ago also GHSA-mrxv-65rv-6hxq , PYSEC-2026-833 , EUVD-2022-4623
- cvss
- 4.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
OpenStack Keystone 2012.1.3 does not invalidate existing tokens when granting or revoking roles, which allows remote authenticated users to retain the privileges of the revoked roles.
Patch / fix
- pypi keystone 2012.1.3
- keystone Debian 14, Debian 13, Debian 12 2012.1.1-6
debian advisories DEBIAN-CVE-2012-4413
- 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-4413 updated cvss 4.0
OpenStack-Keystone: role revocation token issues
-
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
1.90% chance of exploitation in the next 30 days, higher than 79% 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:N/I:P/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | keystone | <2012.1.3 |
2012.1.3 |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
github.com
/openstack/keystone/commit/58ac6691a21675be9e2ffb0f84a05fc3cd4d2e2e
web
-
ubuntu.com
/usn/USN-1564-1
vendor-advisory, web
-
secunia.com
/advisories/50531
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/50590
third-party-advisory, vendor-advisory
-
osvdb.org
/85484
vdb-entry
-
openwall.com
/lists/oss-security/2012/09/12/7
mailing-list, web
-
exchange.xforce.ibmcloud.com
/vulnerabilities/78478
vdb-entry, web
-
securityfocus.com
/bid/55524
vdb-entry
-
nvd.nist.gov
/vuln/detail/CVE-2012-4413
advisory
-
access.redhat.com
/errata/RHSA-2012:1378
web
-
access.redhat.com
/security/cve/CVE-2012-4413
web
-
bugs.launchpad.net
/keystone/+bug/1041396
web
-
bugzilla.redhat.com
/show_bug.cgi?id=855491
web
-
opendev.org
/openstack/keystone
package
-
review.opendev.org
/c/openstack/keystone/+/12870
web
-
web.archive.org
/web/20121114023848/http://www.securityfocus.com/bid/55524
web
-
pypi.org
/project/keystone
package
-
github.com
/advisories/GHSA-mrxv-65rv-6hxq
advisory
Sources
- CVE List CVE-2012-4413
- GitHub Advisory GHSA-mrxv-65rv-6hxq
- NVD CVE-2012-4413
- OSV PYSEC-2026-833
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.