Vulnerability in keystone
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2012-5571 has been found in keystone.
Risk of unauthorized operations or information disclosure.
What to do: upgrade keystone to 8.0.0a0 or later.
If unsure, ask your IT team or search "keystone CVE-2012-5571" on the vendor's site.
CVE-2012-5571 (keystone) — CWE-639
Attack vector: remote (network-reachable) / no user interaction
Patched: 8.0.0a0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-639) exists in keystone.
Check the vendor advisory for the affected versions of keystone.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 8.0.0a0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'keystone' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'keystone' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
keystoneを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade keystone to 8.0.0a0ステージング環境で 8.0.0a0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Package | Affected → Fixed | |
|---|---|---|
| PyPIkeystone |
< 8.0.0a0→ 8.0.0a0 |
8.0.0a0 |
| Red HatOpenStack Essex for RHEL 6 | — | Not listed |
| Red HatOpenStack Folsom for RHEL 6 | — | Not listed |
| Red HatRed Hat OpenStack Platform 13 (Queens) | — | Not listed |
| Red HatRed Hat OpenStack Platform 16.2 | — | Not listed |
| Red HatRed Hat OpenStack Platform 17.1 | — | Not listed |
| Red HatRed Hat OpenStack Platform 18.0 | — | Not listed |
Fix status by distribution
Records published by each distribution for this CVE. Fixed versions differ by release; check each link.
- Debian DEBIAN-CVE-2012-5571 keystone Fix available
Original description The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch openwall.com
- patch openwall.com
- patch secunia.com
- patch secunia.com
- patch bugs.launchpad.net
- patch github.com
- patch github.com
- patch github.com
- web ubuntu.com
- web rhn.redhat.com
- web lists.fedoraproject.org
- web rhn.redhat.com
- web securityfocus.com
- web exchange.xforce.ibmcloud.com
- web secalert@redhat.com
- web github.com
- web secalert@redhat.com
- web secalert@redhat.com