GHSA-qvpr-qm6w-6rcc CVE-2012-5571 PYSEC-2012-35
OpenStack Keystone intended authorization restrictions bypass
- Severity
- 5.4 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 2.05%
- Chance of exploitation in the next 30 days. Higher than 81.28% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-639 Authorization Bypass Through User-Controlled Key
- Fix
8.0.0a0- Upgrade keystone to this version or later
Description
OpenStack Keystone Essex (2012.1) and Folsom (2012.2) does not properly handle EC2 tokens when the user role has been removed from a tenant, which allows remote authenticated users to bypass intended authorization restrictions by leveraging a token for the removed user role.
Affected versions
PyPI
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
keystone PyPI → 8.0.0a0
- pip
pip install --upgrade "keystone>=8.0.0a0"- poetry
poetry add "keystone>=8.0.0a0"- uv
uv add "keystone>=8.0.0a0"
Severity breakdown
CVSS 3.1 5.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
Weakness
CWE-639: Authorization Bypass Through User-Controlled Key
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
How to prevent it
- Architecture and Design: For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
- Architecture and Design, Implementation: Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
- Architecture and Design: Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
References
Advisories
Packages
Other links
- github.com/openstack/keystone/commit/37308dd4f3e33f7bd0f71d83fd51734d1870713b
- github.com/openstack/keystone/commit/8735009dc5b895db265a1cd573f39f4acfca2a19
- github.com/openstack/keystone/commit/9d68b40cb9ea818c48152e6c712ff41586ad9653
- access.redhat.com/security/cve/CVE-2012-5571
- bugs.launchpad.net/keystone/+bug/1064914
- exchange.xforce.ibmcloud.com/vulnerabilities/80333
- github.com/pypa/advisory-database/tree/main/vulns/keystone/PYSEC-2012-35.yaml
- lists.fedoraproject.org/pipermail/package-announce/2012-December/094286.html
- rhn.redhat.com/errata/RHSA-2012-1556.html
- rhn.redhat.com/errata/RHSA-2012-1557.html
- openwall.com/lists/oss-security/2012/11/28/5
- openwall.com/lists/oss-security/2012/11/28/6
- ubuntu.com/usn/USN-1641-1
- securityfocus.com/bid/56726
- access.redhat.com/errata/RHSA-2012:1556
- access.redhat.com/errata/RHSA-2012:1557
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-whqr-fgm5-x77q OpenStack Keystone's federated token rescoping mechanism doesn't propagate the original token's expiry to the newly issued token | High | Also affects keystone |
| GHSA-q623-f4j4-p4xj OpenStack Keystone has an Incorrect Authorization issue | High | Also affects keystone |
| GHSA-2r23-2g6v-2m5f OpenStack Keystone has an Authorization Bypass | High | Also affects keystone |
| GHSA-8f8m-wrvr-wcvf OpenStack Keystone doesn't verify that the user supplied in the authentication request matches the owner of the application credential | High | Also affects keystone |
| GHSA-hhq2-3832-xxcv OpenStack Keystone has an Incorrect Authorization Issue | High | Also affects keystone |
| GHSA-pfx2-9x9m-7ghx OpenStack Keystone: LDAP identity backend does not convert enabled attribute to boolean | High | Also affects keystone |
| GHSA-4phw-6824-6cfp OpenStack Keystone: Restricted application credentials can create EC2 credentials | Medium | Also affects keystone |
| GHSA-hcqg-5g63-7j9h OpenStack Keystone allows /v3/ec2tokens or /v3/s3tokens request with valid AWS Signature to provide Keystone authorization. | High | Also affects keystone |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor