← Back
CVE-2012-3371
Vulnerability in nova (CVE-2012-3371)
Summary
vulnerability in nova (CVE-2012-3371). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `034762e8060dcf0a11cb039b9d426b0d0bb1801d` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2012-3371** has been found in nova.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade nova to **034762e8060dcf0a11cb039b9d426b0d0bb1801d** or later.
If unsure, ask your IT team or search "nova CVE-2012-3371" on the vendor's site.
CVE-2012-3371 (nova) —
Patched: `034762e8060dcf0a11cb039b9d426b0d0bb1801d` — 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 nova.
📍 Affected scope
nova — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **034762e8060dcf0a11cb039b9d426b0d0bb1801d**.
🛡️ 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 'nova' .` 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 'nova' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `nova` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade nova to 034762e8060dcf0a11cb039b9d426b0d0bb1801dステージング環境で 034762e8060dcf0a11cb039b9d426b0d0bb1801d に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
nova
[{"repo":"https:\/\/github.com\/openstack\/nova","type":"GIT","events":[{"introduced":"0"},{"fixed":"034762e8060dcf0a11cb039b9d426b0d0bb1801d"}]},{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
References
- advisory http://www.ubuntu.com/usn/USN-1501-1
- advisory https://github.com/advisories/GHSA-xxgm-qpj5-4886
- patch https://github.com/openstack/nova/commit/034762e8060dcf0a11cb039b9d426b0d0bb1801d
- report https://bugs.launchpad.net/nova/+bug/1017795
- web http://www.openwall.com/lists/oss-security/2012/07/11/13
- web https://lists.launchpad.net/openstack/msg14452.html
- web http://www.securityfocus.com/bid/54388