| Name | CVE-2013-2104 |
| Description | 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. |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| keystone (PTS) | bullseye | 2:18.0.0-3+deb11u1 | fixed |
| bookworm | 2:22.0.0-2 | fixed |
| sid, trixie | 2:26.0.0-1 | fixed |
| python-keystoneclient (PTS) | bullseye | 1:4.1.1-2 | fixed |
| bookworm | 1:5.0.1-3 | fixed |
| sid, trixie | 1:5.5.0-2 | fixed |
The information below is based on the following data on fixed versions.
Notes
- keystone <not-affected> (Vulnerable code only in experimental versions of keystone)
[wheezy] - keystone <not-affected> (PKI token support not yet present)
[wheezy] - python-keystoneclient <not-affected> (vulnerable code not present)
Keystone Folsom fix: https://review.openstack.org/#/c/30743/
python-keystoneclient fix: https://review.openstack.org/#/c/30742/
Starting with 2013.1-1 code in keystone/middleware/auth_token.py moved to python-keystoneclient