Skip to content
Fencer Intel
high 7.5

CVE-2013-2104 json

python-keystoneclient missing expiration check in PKI token validation

published 2014-01-21 12 y ago modified 2026-06-16 4 mo ago also GHSA-4rrr-j7ff-r844 , PYSEC-2014-69 , EUVD-2014-0091

cvss
7.5
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
2.1%
EPSS 2.1% chance of exploitation in 30 days, percentile 82%
public exploits
0
none known

Summary

python-keystoneclient before 0.2.4, as used in OpenStack Keystone (Folsom), does not properly check expiry for PKI tokens, which allows remote authenticated users to (1) retain use of a token after it has expired, or (2) use a revoked token once it expires.

Patch / fix

  • pypi python-keystoneclient 0.2.4
  • python-keystoneclient Debian 14, Debian 13, Debian 12 1:0.2.5-1

debian advisories DEBIAN-CVE-2013-2104

  • python-keystoneclient openstack 3 1:0.2.3-2.el6ost

red hat advisories RHSA-2013:0944

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-2013-2104 updated cvss 2.6

Keystone: Missing expiration check in Keystone PKI token validation

  • Red Hat Enterprise Linux OpenStack Platform 3.0 python-keystoneclient 0.2.3-2.el6ost
    fixed: vendor fix RHSA-2013:0944

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

CVSS scores

assigned by version score vector
NVD 2.0 5.5 AV:N/AC:L/Au:S/C:N/I:P/A:P
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
pypi python-keystoneclient
<0.2.4
0.2.4

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls
  • CWE-324 Use of a Key Past its Expiration Date

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.