CVE-2023-32314 — AI Deep Analysis Summary

Q: Who is affected? (Versions/Components)

📦 **Affected**: `vm2` library by **Patrik Simek**. 📉 **Versions**: **3.9.17 and earlier**. ⚠️ **Status**: Fixed in version **3.9.18**.

Q: What can hackers do? (Privileges/Data)

👑 **Privileges**: Full **System Access**. 📂 **Data**: Complete **Confidentiality, Integrity, and Availability** loss. Attackers can read files, modify data, and crash services.

Q: Is exploitation threshold high? (Auth/Config)

🔓 **Threshold**: **LOW**. 🌐 **Network**: Attack Vector is **Network** (AV:N). 🔑 **Auth**: **No Privileges** required (PR:N). 👀 **UI**: **No User Interaction** needed (UI:N).

Q: Is there a public Exp? (PoC/Wild Exploitation)

💣 **Public Exploit**: **YES**. 📂 **PoC**: Available via GitHub Gists and repositories demonstrating RCE in Node.js apps using vulnerable `vm2` versions.

Q: Is it fixed officially? (Patch/Mitigation)

✅ **Fixed**: **YES**. 🔧 **Patch**: Upgrade to **vm2 v3.9.18** or later. 🔗 **Ref**: See GitHub Security Advisory (GHSA-whpj-8f3w-67p5) and release notes.

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **CRITICAL**. 🚨 **Priority**: **P1**. 📈 **CVSS**: **9.8** (High). ⏱️ **Action**: Patch immediately. This is a trivial RCE with no auth needed.

Updated May 08, 2026 CVSS 9.8 · Critical

This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis →

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: `vm2` (Node.js sandbox) has an **Injection Vulnerability**. <br>💥 **Consequences**: Attackers can bypass the sandbox and execute arbitrary code.…

Read full answer (login)

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **CWE-74** (Improper Neutralization of Special Elements). <br>🔍 **Flaw**: The sandbox allows running untrusted code using **whitelisted Node.js built-in modules**.…

Read full answer (login)

Q3Who is affected? (Versions/Components)

📦 **Affected**: `vm2` library by **Patrik Simek**. <br>📉 **Versions**: **3.9.17 and earlier**. <br>⚠️ **Status**: Fixed in version **3.9.18**.

Q4What can hackers do? (Privileges/Data)

👑 **Privileges**: Full **System Access**. <br>📂 **Data**: Complete **Confidentiality, Integrity, and Availability** loss. Attackers can read files, modify data, and crash services.

Q5Is exploitation threshold high? (Auth/Config)

🔓 **Threshold**: **LOW**. <br>🌐 **Network**: Attack Vector is **Network** (AV:N). <br>🔑 **Auth**: **No Privileges** required (PR:N). <br>👀 **UI**: **No User Interaction** needed (UI:N).

Q6Is there a public Exp? (PoC/Wild Exploitation)

💣 **Public Exploit**: **YES**. <br>📂 **PoC**: Available via GitHub Gists and repositories demonstrating RCE in Node.js apps using vulnerable `vm2` versions.

Q7How to self-check? (Features/Scanning)

🔍 **Self-Check**: Scan your `package.json` or `node_modules` for `vm2`. <br>📊 **Version Check**: If version is **≤ 3.9.17**, you are vulnerable.…

Read full answer (login)

Q8Is it fixed officially? (Patch/Mitigation)

✅ **Fixed**: **YES**. <br>🔧 **Patch**: Upgrade to **vm2 v3.9.18** or later. <br>🔗 **Ref**: See GitHub Security Advisory (GHSA-whpj-8f3w-67p5) and release notes.

Q9What if no patch? (Workaround)

🚧 **No Patch?**: **Mitigation**. <br>🚫 **Restrict**: Do not use `vm2` for untrusted code. <br>🛡️ **Isolate**: Run Node.js processes in strict containers with minimal permissions.…

Read full answer (login)

Q10Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **CRITICAL**. <br>🚨 **Priority**: **P1**. <br>📈 **CVSS**: **9.8** (High). <br>⏱️ **Action**: Patch immediately. This is a trivial RCE with no auth needed.

Continue exploring

Vulnerability detail Full AI analysis (login) patriksimek CWE-74