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 disclo
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 16.0.2, 17.0.1, 18.0.1, 19.0.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- n/a n/a
Version range not reported
- keystonePyPI
From 10.0 · fixed in 16.0.2; From 17.0 · fixed in 17.0.1; From 18.0 · fixed in 18.0.1; From 19.0 · fixed in 19.0.1
- keystonePyPI
From 10.0 · fixed in 16.0.2
- keystonePyPI
From 17.0 · fixed in 17.0.1
- keystonePyPI
From 18.0 · fixed in 18.0.1
- keystonePyPI
From 19.0 · fixed in 19.0.1