Skip to content

GHSA-4225-97pr-rr52 CVE-2021-38155 PYSEC-2026-830

OpenStack Keystone allows information disclosure during account locking

High PyPI
Severity
7.5 / 10
High · CVSS 3.1
Exploit chance (EPSS)
2.48%
Chance of exploitation in the next 30 days. Higher than 84.56% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-307 Improper Restriction of Excessive Authentication Attempts
Fix
16.0.2
Upgrade keystone to this version or later

Description

OpenStack Keystone 10.x through 16.x before 16.0.2, 17.x before 17.0.1, 18.x before 18.0.1, and 19.x before 19.0.1 allows information disclosure during account locking (related to PCI DSS features). By guessing the name of an account and failing to authenticate multiple times, any unauthenticated actor could both confirm the account exists and obtain that account's corresponding UUID, which might be leveraged for other unrelated attacks. All deployments enabling security_compliance.lockout_failure_attempts are affected.

Affected versions

PyPI

PackageVulnerableFixed in
keystone
>= 10.0, < 16.0.2
16.0.2
keystone
>= 17.0, < 17.0.1
17.0.1
keystone
>= 18.0, < 18.0.1
18.0.1
keystone
>= 19.0, < 19.0.1
19.0.1
keystone
>= 10.0, < 16.0.2
>= 17.0, < 17.0.1
>= 18.0, < 18.0.1
>= 19.0, < 19.0.1
16.0.2
17.0.1
18.0.1
19.0.1

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 → 16.0.2

pip
pip install --upgrade "keystone>=16.0.2"
poetry
poetry add "keystone>=16.0.2"
uv
uv add "keystone>=16.0.2"

Severity breakdown

CVSS 3.1 7.5

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

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

Weakness

CWE-307: Improper Restriction of Excessive Authentication Attempts

The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame.

How to prevent it
  • Architecture and Design: Common protection mechanisms include: Disconnecting the user after a small number of failed attempts Implementing a timeout Locking out a targeted account Requiring a computational task on the user's part.
  • Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. Consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator. [REF-45]

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