Skip to content
Log inStart free trial

GHSA-v8fq-gq9j-3v7h CVE-2014-5252 PYSEC-2014-108

OpenStack Identity (Keystone) UUID v2 tokens does not expire with revocation events

Medium PyPI
Severity
0.0 / 10
Medium · CVSS 4.0
Exploit chance (EPSS)
1.52%
Chance of exploitation in the next 30 days. Higher than 74.52% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-613 Insufficient Session Expiration
Fix
8.0.0a0
Upgrade keystone to this version or later

Description

The V3 API in OpenStack Identity (Keystone) 2014.1.x before 2014.1.2.1 and Juno before Juno-3 updates the issued_at value for UUID v2 tokens, which allows remote authenticated users to bypass the token expiration and retain access via a verification (1) GET or (2) HEAD request to v3/auth/tokens/.

Affected versions

PyPI

PackageVulnerableFixed in
keystone
< 8.0.0a0
8.0.0a0

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"

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
Low
User interaction
None
Confidentiality (vulnerable system)
None
Integrity (vulnerable system)
High
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None

CVSS 3.1 6.5

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Weakness

CWE-613: Insufficient Session Expiration

According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."

How to prevent it
  • Implementation: Set sessions/credentials expiration date.

References

Advisories

Packages

Other links

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy 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
Is this in your code?

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