LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38155: 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...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Keystone could reveal whether an account name exists and expose that account’s UUID during repeated failed login attempts. This affects OpenStack deployments that enabled the PCI DSS-related account lockout setting. The issue is information disclosure, not direct account takeover, but it can support later targeting. Exposure is limited to OpenStack Keystone deployments running affected versions and enabling security_compliance.lockout_failure_attempts. Publicly reachable Keystone authentication endpoints increase practical risk. The bundle does not identify other affected products. Treat this as a targeted information disclosure risk for OpenStack environments, especially internet-exposed identity services. Prioritize patching where account lockout is enabled or where Keystone is reachable by untrusted users. Mitigation focus: Upgrade Keystone to fixed releases: 16.0.2, 17.0.1, 18.0.1, or 19.0.1 as applicable.; Apply downstream security updates where Keystone is packaged by a distribution, such as Debian LTS guidance.; Check OpenStack vendor guidance before changing lockout configuration as a temporary risk decision..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-38155 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.