Skip to content

OpenStack Keystone allows information disclosure during account locking

High severity GitHub Reviewed Published May 24, 2022 to the GitHub Advisory Database • Updated May 14, 2024

Package

pip keystone (pip)

Affected versions

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

Patched versions

16.0.2
17.0.1
18.0.1
19.0.1

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.

References

Published by the National Vulnerability Database Aug 6, 2021
Published to the GitHub Advisory Database May 24, 2022
Last updated May 14, 2024
Reviewed May 14, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.171%
(55th percentile)

Weaknesses

CVE ID

CVE-2021-38155

GHSA ID

GHSA-4225-97pr-rr52

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.