Description (CNA)
An issue was discovered in OpenStack Keystone before 29.0.2. POST /v3/credentials did not validate that the caller-supplied project_id for an EC2-type credential matched the project of the authenticating application credential. This allowed an attacker holding an unrestricted application credential for project A to create an EC2 credential targeting project B; a subsequent /v3/ec2tokens exchange would then issue a Keystone token scoped to project B while still carrying the original app_cred_id, enabling cross-project lateral movement within the credential owner's role footprint.
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| OpenStack / Keystone | affected 14.0.0 before 27.0.2; affected 28.0.0 before 28.0.2; affected 29.0.0 before 29.0.2 |
CWE
CWE-863
References
- https://bugs.launchpad.net/keystone/+bug/2149775
- https://review.opendev.org/c/openstack/keystone/+/985804
- https://security.openstack.org/ossa/OSSA-2026-015.html
ADP enrichment
No English description supplied.
No references supplied.
A flaw was found in OpenStack Keystone. An attacker holding an unrestricted application credential could exploit a vulnerability in the POST /v3/credentials endpoint where the caller-supplied project_id for an EC2-type credential was not validated against the project of the authenticating application credential. This allows the attacker to create an EC2 credential targeting a different project. Subsequently, a /v3/ec2tokens exchange would issue a Keystone token scoped to the targeted project, enabling unauthorized cross-project access and lateral movement within the credential owner's role footprint.