# CVE-2013-2104: python-keystoneclient missing expiration check in PKI token validation

Source: https://junglewise.ai/threats/cve-2013-2104-python-keystoneclient-missing-expiration-check-in-pki-token  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2014-01-21  
License: CC BY 4.0 with a link back

CVE-2013-2104 · Severity: low · CVSS 3.1 · Published 2014-01-21

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.

Technologies: [python-keystoneclient (PyPI)](https://junglewise.ai/threats/technologies/python-keystoneclient). Vendors: [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2013-2104 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2013-2104 being exploited in the wild.

**How severe is CVE-2013-2104?** Low severity, with a CVSS score of 3.1, published 21 January 2014.

**Which products and versions are affected?** python-keystoneclient (PyPI) ECOSYSTEM:introduced=0,fixed=0.2.4.

**Is there a fix for CVE-2013-2104?** Yes. python-keystoneclient (PyPI): upgrade to 0.2.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2013-2104?** Check whether you run python-keystoneclient (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- python-keystoneclient (PyPI): upgrade to 0.2.4 or later

  ```sh
  pip install "python-keystoneclient>=0.2.4"
  ```


## Affected products

- python-keystoneclient (PyPI) ECOSYSTEM:introduced=0,fixed=0.2.4

## Identifiers

- CVE-2013-2104
- GHSA-4rrr-j7ff-r844
- PYSEC-2014-69

## Related threats

- [PYSEC-2026-911 - OpenStack Nova uses insecure keystone middleware tmpdir by default](https://junglewise.ai/threats/cve-2013-2030-openstack-nova-uses-insecure-keystone-middleware-tmpdir-by-default)
- [PYSEC-2026-656 - OpenStack Keystone and other components vulnerable to Improper Certificate Validation](https://junglewise.ai/threats/cve-2013-2255-openstack-keystone-and-other-components-vulnerable-to-improper)
- [PYSEC-2019-161 - python-keystoneclient version 0.2.3 to 0.2.5 has middleware memcache signing bypass](https://junglewise.ai/threats/cve-2013-2167-insufficient-verification-of-data-authenticity-in-python)
- [PYSEC-2019-197 - python-keystoneclient version 0.2.3 to 0.2.5 has middleware memcache encryption bypass](https://junglewise.ai/threats/cve-2013-2166-inadequate-encryption-strength-in-python-keystoneclient)
- [OpenStack keystonemiddleware and python-keystoneclient vulnerable to man-in-the-middle attacks](https://junglewise.ai/threats/cve-2015-1852-openstack-keystonemiddleware-and-python-keystoneclient-vulnerable)