Vulnerability in keystone (CVE-2012-3426)

Summary

vulnerability in keystone (CVE-2012-3426). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `ea03d05ed5de0c015042876100d37a6a14bf56de, 628149b3dc6b58b91fd08e6ca8d91c728ccb8626, 375838cfceb88cacc312ff6564e64eb18ee6a355, d9600434da14976463a0bd03abd8e0309f0db454, 29e74e73a6e51cffc0371b32354558391826a4aa, a67b24878a6156eab17b9098fa649f0279256f5d` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2012-3426** has been found in keystone. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade keystone to **ea03d05ed5de0c015042876100d37a6a14bf56de, 628149b3dc6b58b91fd08e6ca8d91c728ccb8626, 375838cfceb88cacc312ff6564e64eb18ee6a355, d9600434da14976463a0bd03abd8e0309f0db454, 29e74e73a6e51cffc0371b32354558391826a4aa, a67b24878a6156eab17b9098fa649f0279256f5d** or later. If unsure, ask your IT team or search "keystone CVE-2012-3426" on the vendor's site.

CVE-2012-3426 (keystone) — Patched: `ea03d05ed5de0c015042876100d37a6a14bf56de, 628149b3dc6b58b91fd08e6ca8d91c728ccb8626, 375838cfceb88cacc312ff6564e64eb18ee6a355, d9600434da14976463a0bd03abd8e0309f0db454, 29e74e73a6e51cffc0371b32354558391826a4aa, a67b24878a6156eab17b9098fa649f0279256f5d` — 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** (unclassified) exists in keystone.

📍 Affected scope

keystone — .

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to **ea03d05ed5de0c015042876100d37a6a14bf56de, 628149b3dc6b58b91fd08e6ca8d91c728ccb8626, 375838cfceb88cacc312ff6564e64eb18ee6a355, d9600434da14976463a0bd03abd8e0309f0db454, 29e74e73a6e51cffc0371b32354558391826a4aa, a67b24878a6156eab17b9098fa649f0279256f5d**.

🛡️ 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

1
Identify exposure identify
```
grep -r 'keystone' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `keystone` を grep し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade keystone to ea03d05ed5de0c015042876100d37a6a14bf56de, 628149b3dc6b58b91fd08e6ca8d91c728ccb8626, 375838cfceb88cacc312ff6564e64eb18ee6a355, d9600434da14976463a0bd03abd8e0309f0db454, 29e74e73a6e51cffc0371b32354558391826a4aa, a67b24878a6156eab17b9098fa649f0279256f5d
```
ステージング環境で ea03d05ed5de0c015042876100d37a6a14bf56de, 628149b3dc6b58b91fd08e6ca8d91c728ccb8626, 375838cfceb88cacc312ff6564e64eb18ee6a355, d9600434da14976463a0bd03abd8e0309f0db454, 29e74e73a6e51cffc0371b32354558391826a4aa, a67b24878a6156eab17b9098fa649f0279256f5d に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

PyPI keystone

[{"repo":"https:\/\/github.com\/openstack\/keystone","type":"GIT","events":[{"introduced":"0"},{"fixed":"ea03d05ed5de0c015042876100d37a6a14bf56de"},{"fixed":"628149b3dc6b58b91fd08e6ca8d91c728ccb8626"},{"fixed":"375838cfceb88cacc312ff6564e64eb18ee6a355"},{"fixed":"d9600434da14976463a0bd03abd8e0309f0db454"},{"fixed":"29e74e73a6e51cffc0371b32354558391826a4aa"},{"fixed":"a67b24878a6156eab17b9098fa649f0279256f5d"}]},{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]