← Back
GHSA-m5w8-4gq2-6f8x
Information Disclosure in vm2 (GHSA-m5w8-4gq2-6f8x)
Summary
vulnerability in vm2 (GHSA-m5w8-4gq2-6f8x). Risk of unauthorized operations or information disclosure. Exploitable via `Host header`. Mitigation: upgrade to `3.11.6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-m5w8-4gq2-6f8x** has been found in vm2.
Attackers can target a specific entry point like `Host header` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade vm2 to **3.11.6** or later.
If unsure, ask your IT team or search "vm2 GHSA-m5w8-4gq2-6f8x" on the vendor's site.
GHSA-m5w8-4gq2-6f8x (vm2) — CWE-200 /
Attack surface: Host header / `dns` / `fetch` / `NodeVM`
Patched: `3.11.6` — 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
**information disclosure** (CWE-200) exists in vm2. Attackers reach the vulnerable code path via `Host header` without authentication.
📍 Affected scope
vm2 — . Attack surface: Host header / `dns` / `fetch` / `NodeVM`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.11.6**.
🛡️ 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 'vm2' .` 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 'vm2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `vm2` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade vm2 to 3.11.6ステージング環境で 3.11.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
vm2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.11.6"}]}]