Skip to content

GHSA-6mv3-p2gr-wgqf CVE-2014-2828 PYSEC-2014-106

OpenStack Identity (Keystone) DoS through V3 API authentication chaining

High PyPI
Severity
0.0 / 10
High · CVSS 4.0
Exploit chance (EPSS)
3.22%
Chance of exploitation in the next 30 days. Higher than 88.21% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-287 Improper Authentication
Fix
8.0.0a0
Upgrade keystone to this version or later

Description

The V3 API in OpenStack Identity (Keystone) 2013.1 before 2013.2.4 and icehouse before icehouse-rc2 allows remote attackers to cause a denial of service (CPU consumption) via a large number of the same authentication method in a request, aka "authentication chaining."

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:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

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

CVSS 3.1 7.5

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

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

Weakness

CWE-287: Improper Authentication

When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

How to prevent it
  • Architecture and Design: Use an authentication framework or library such as the OWASP ESAPI Authentication feature.

References

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