OpenStack Keystone has an Incorrect Authorization Issue
OpenStack Keystone
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| keystone PyPI |
|
|
OpenStack Keystone
| Product | Affected | Fixed in |
|---|---|---|
| keystone PyPI |
|
|
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.
From the CVE record · mitre
OpenStack Keystone did not check that the project_id supplied when creating an EC2-type credential matched the project of the authenticating application credential. An attacker with an unrestricted application credential for one project can use the credential and EC2 token APIs to obtain a token scoped to another project, within the credential owner's role footprint.
Operators running the PyPI keystone package should check affected releases from 13.0.0 through 29.0.1, including the listed 27.x, 28.x, and 29.x ranges.