← Back
CVE-2012-5571
Vulnerability in keystone (CVE-2012-5571)
Summary
vulnerability in keystone (CVE-2012-5571). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `8.0.0a0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2012-5571** has been found in keystone.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
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.
❓ What is the problem
**A vulnerability** (CWE-639) exists in keystone.
📍 Affected scope
keystone — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **8.0.0a0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'keystone' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `keystone` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade keystone to 8.0.0a0ステージング環境で 8.0.0a0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
keystone
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.0a0"}]}]
References
- advisory http://secunia.com/advisories/51423
- advisory http://secunia.com/advisories/51436
- advisory https://github.com/advisories/GHSA-qvpr-qm6w-6rcc
- advisory https://nvd.nist.gov/vuln/detail/CVE-2012-5571
- package https://github.com/openstack/keystone
- web http://www.openwall.com/lists/oss-security/2012/11/28/5
- web http://www.openwall.com/lists/oss-security/2012/11/28/6
- web http://www.ubuntu.com/usn/USN-1641-1
- web https://bugs.launchpad.net/keystone/+bug/1064914
- web https://github.com/openstack/keystone/commit/37308dd4f3e33f7bd0f71d83fd51734d1870713b
- web https://github.com/openstack/keystone/commit/8735009dc5b895db265a1cd573f39f4acfca2a19
- web https://github.com/openstack/keystone/commit/9d68b40cb9ea818c48152e6c712ff41586ad9653
- web http://rhn.redhat.com/errata/RHSA-2012-1556.html
- web http://lists.fedoraproject.org/pipermail/package-announce/2012-December/094286.html
- web http://rhn.redhat.com/errata/RHSA-2012-1557.html
- web http://www.securityfocus.com/bid/56726
- web https://exchange.xforce.ibmcloud.com/vulnerabilities/80333
- web https://access.redhat.com/security/cve/CVE-2012-5571
- web https://github.com/pypa/advisory-database/tree/main/vulns/keystone/PYSEC-2012-35.yaml