Skip to content
Fencer Intel
medium 4.9

CVE-2012-3426 json

OpenStack Keystone token expiration issues

published 2012-07-31 14 y ago modified 2026-06-16 4 mo ago also GHSA-xp97-6w7r-4cjc , PYSEC-2012-34 , EUVD-2012-0015

cvss
4.9
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 before 2012.1.1, as used in OpenStack Folsom before Folsom-1 and OpenStack Essex, does not properly implement token expiration, which allows remote authenticated users to bypass intended authorization restrictions by (1) creating new tokens through token chaining, (2) leveraging possession of a token for a disabled user account, or (3) leveraging possession of a token for an account with a changed password.

Patch / fix

  • pypi keystone 8.0.0a0
  • keystone Debian 14, Debian 13, Debian 12 2012.1.1-1

debian advisories DEBIAN-CVE-2012-3426

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-3426 updated cvss 4.9

OpenStack-Keystone: token expiration issues

  • 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.30% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com http://github.com/openstack/keystone/commit/ea03d05ed5de0c015042876100d37a6a14bf56de referenced PoC, tagged "exploit" by a source, unverified
  • github.com http://github.com/openstack/keystone/commit/628149b3dc6b58b91fd08e6ca8d91c728ccb8626 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected packages

ecosystem package affected fixed in
pypi keystone
<8.0.0a0
8.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.