CyberRota Analysis
AI-GeneratedOpenStack Keystone versions prior to 29.0.3 are vulnerable to a token reauthentication flaw that allows tokens obtained through delegated authentication mechanisms to bypass project boundaries, potentially granting unauthorized access to resources. This vulnerability can lead to privilege escalation within the OpenStack environment, making it critical for organizations using Keystone with OAuth1 access tokens, application credentials, or trusts to prioritize an upgrade to mitigate risks. All Keystone deployments utilizing these authentication methods should assess their exposure and apply the necessary patches promptly.
Original NVD Description
In OpenStack Keystone before 29.0.3, tokens obtained via delegated authentication mechanisms (OAuth1 access tokens, application credentials, trusts) could be submitted to the token-method authentication path for reauthentication to escape their intended project scope. When an application credential token was presented with no explicit scope, Keystone would issue a new token scoped to the credential owner's default project rather than the project for which the credential was issued, bypassing the intended project boundary. All Keystone deployments that permit delegated authentication through OAuth1 access tokens, application credentials, or trusts are affected.