GHSA-xp97-6w7r-4cjc CVE-2012-3426 PYSEC-2012-34
OpenStack Keystone token expiration issues
- Severity
- Medium
- The publisher's own rating, not a CVSS score
- Exploit chance (EPSS)
- 2.30%
- Chance of exploitation in the next 30 days. Higher than 83.27% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- —
- Not classified
- Fix
8.0.0a0- Upgrade keystone to this version or later
Description
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.
Affected versions
PyPI
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
keystone PyPI → 8.0.0a0
- pip
pip install --upgrade "keystone>=8.0.0a0"- poetry
poetry add "keystone>=8.0.0a0"- uv
uv add "keystone>=8.0.0a0"
References
Advisories
Packages
Other links
- github.com/openstack/keystone/commit/375838cfceb88cacc312ff6564e64eb18ee6a355
- github.com/openstack/keystone/commit/628149b3dc6b58b91fd08e6ca8d91c728ccb8626
- github.com/openstack/keystone/commit/a67b24878a6156eab17b9098fa649f0279256f5d
- bugs.launchpad.net/keystone/+bug/996595
- bugs.launchpad.net/keystone/+bug/997194
- bugs.launchpad.net/keystone/+bug/998185
- github.com/pypa/advisory-database/tree/main/vulns/keystone/PYSEC-2012-34.yaml
- launchpad.net/keystone/essex/2012.1.1/+download/keystone-2012.1.1.tar.gz
- github.com/openstack/keystone/commit/29e74e73a6e51cffc0371b32354558391826a4aa
- github.com/openstack/keystone/commit/375838cfceb88cacc312ff6564e64eb18ee6a355
- github.com/openstack/keystone/commit/628149b3dc6b58b91fd08e6ca8d91c728ccb8626
- github.com/openstack/keystone/commit/a67b24878a6156eab17b9098fa649f0279256f5d
- github.com/openstack/keystone/commit/d9600434da14976463a0bd03abd8e0309f0db454
- github.com/openstack/keystone/commit/ea03d05ed5de0c015042876100d37a6a14bf56de
- openwall.com/lists/oss-security/2012/07/27/4
- ubuntu.com/usn/USN-1552-1
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-whqr-fgm5-x77q OpenStack Keystone's federated token rescoping mechanism doesn't propagate the original token's expiry to the newly issued token | High | Also affects keystone |
| GHSA-q623-f4j4-p4xj OpenStack Keystone has an Incorrect Authorization issue | High | Also affects keystone |
| GHSA-2r23-2g6v-2m5f OpenStack Keystone has an Authorization Bypass | High | Also affects keystone |
| GHSA-8f8m-wrvr-wcvf OpenStack Keystone doesn't verify that the user supplied in the authentication request matches the owner of the application credential | High | Also affects keystone |
| GHSA-hhq2-3832-xxcv OpenStack Keystone has an Incorrect Authorization Issue | High | Also affects keystone |
| GHSA-pfx2-9x9m-7ghx OpenStack Keystone: LDAP identity backend does not convert enabled attribute to boolean | High | Also affects keystone |
| GHSA-4phw-6824-6cfp OpenStack Keystone: Restricted application credentials can create EC2 credentials | Medium | Also affects keystone |
| GHSA-hcqg-5g63-7j9h OpenStack Keystone allows /v3/ec2tokens or /v3/s3tokens request with valid AWS Signature to provide Keystone authorization. | High | Also affects keystone |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor