Security readout for executives and security teams
Plain-English summary
CVE-2023-37466 lets malicious JavaScript break out of vm2's intended sandbox in affected versions. If an application uses vm2 to run untrusted code, the attacker may gain arbitrary code execution in that sandboxed Node.js context. This is business-critical where vm2 separates tenants, plugins, or user code.
Executive priority
Treat as urgent wherever vm2 protects trust boundaries or runs customer-controlled code. The library is discontinued, so a one-time patch is not a durable risk reduction strategy; replacement planning should be prioritized after immediate exposure checks.
Technical view
In vm2 <=3.9.19, Promise handler sanitization can be bypassed using the @@species accessor property. The advisory describes sandbox escape and arbitrary code execution, mapped to CWE-94, with CVSS 9.8. Version 3.10.0 patched this issue, but the bundle states vm2 maintenance is discontinued and production use is not recommended.
Likely exposure
Exposure is most likely in Node.js services that depend on patriksimek/vm2 <=3.9.19 and execute untrusted or semi-trusted JavaScript. Risk also exists through transitive dependencies or vendor products embedding vm2, including products covered by downstream vendor advisories.
Exploitation context
The provided sources support critical remote-code-execution potential but do not state active exploitation. KEV status is false in the bundle. Practical impact depends on whether attackers can supply JavaScript that the application runs inside vm2.
Researcher notes
The key condition is attacker influence over code evaluated inside vm2. Validate dependency version and reachable execution paths before rating local exposure. The source bundle provides a patch reference but no evidence of active exploitation or broader affected product inventory.
Mitigation direction
- Upgrade affected vm2 installations to version 3.10.0 or later where feasible.
- Plan migration away from vm2 for production sandboxing due to discontinued maintenance.
- Check vendor advisories for products that may bundle vm2 internally.
- Restrict who can submit code executed inside vm2 until replacement is complete.
- Review compensating isolation around systems that run untrusted JavaScript.
Validation and detection
- Search dependency manifests and lockfiles for vm2 versions <=3.9.19.
- Check software composition analysis results for direct and transitive vm2 usage.
- Identify application features that execute user, tenant, plugin, or workflow JavaScript.
- Confirm deployed artifacts match the patched or removed dependency state.
- Review vendor notices for appliances or platforms using bundled Node.js components.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-37466 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/patriksimek/vm2/security/advisories/GHSA-cchq-frgv-rjh5CVE reference · x_refsource_CONFIRM
- https://github.com/patriksimek/vm2/commit/d9a1fde8ec5a5a9c9e5a69bf91d703950859d744CVE reference · x_refsource_MISC
- https://github.com/patriksimek/vm2/releases/tag/v3.10.0CVE reference · x_refsource_MISC
- https://security.netapp.com/advisory/ntap-20241108-0002/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.