An issue was discovered in OpenStack Keystone before 29.0.2.
- 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 27.0.2, 28.0.2, 29.0.2
- 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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
An issue was discovered in OpenStack Keystone before 29.0.2. The Keystone application credential authentication plugin does not verify that the user supplied in the authentication request matches the owner of the application credential. An attacker can authenticate with their own application credential ID and secret while specifying a different user's name and domain in the request body. Keystone issues a token attributed to the victim user. The impersonated token is project-scoped and carries the intersection of the application credential's roles and the victim's actual roles on the project. This enables audit evasion, reading the victim's credentials, and acting as the victim within shared projects.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- OpenStack Keystone
From 14.0.0 · fixed in 27.0.2; From 28.0.0 · fixed in 28.0.2; From 29.0.0 · fixed in 29.0.2
- keystonePyPI
From 14.0.0 · fixed in 27.0.2
- keystonePyPI
From 28.0.0 · fixed in 28.0.2
- keystonePyPI
From 29.0.0 · fixed in 29.0.2
- keystonePyPI
From 14.0.0 · fixed in 27.0.2; From 28.0.0 · fixed in 28.0.2; From 29.0.0 · fixed in 29.0.2