dbcve.org
Vm2Application · Vm2 Project

CVE-2022-36067

CRITICAL · 10.0 CVSS v3.1 Published 2022-09-06
Fix available
A fix is available. Upgrade to 3.9.11 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
vm2 is a sandbox that can run untrusted code with whitelisted Node's built-in modules. In versions prior to version 3.9.11, a threat actor can bypass the sandbox protections to gain remote code execution rights on the host running the sandbox. This vulnerability was patched in the release of version 3.9.11 of vm2. There are no known workarounds.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

vm2 is a JavaScript sandbox library that allows running untrusted code with whitelisted Node.js built-in modules. In versions prior to 3.9.11, a vulnerability allows threat actors to bypass sandbox protections and achieve remote code execution on the host system. This is a complete sandbox escape enabling full compromise of the host.

MitigationUpgrade vm2 to version 3.9.11 or later; there are no workarounds available for earlier versions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Vm2Application
Affected:< 3.9.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate vm2 in your project dependencies
    Search your project's package.json files for 'vm2' in the dependencies or devDependencies sections, or run 'npm list vm2' in your project root to see if it's installed as a direct or transitive dependency
    Affected if vm2 appears in your dependency tree
  2. Determine the installed vm2 version
    Run 'npm list vm2' or check the version field in node_modules/vm2/package.json to identify the exact version number installed
    Affected if The version shown is lower than 3.9.11 (for example, 3.9.10, 3.9.9, etc.)
  3. Verify vm2 is actively used in your codebase
    Search your application source code for require('vm2') or import statements bringing in vm2, and identify where the sandbox is created to run untrusted code
    Affected if Your code imports and invokes vm2 to execute untrusted JavaScript code within the sandbox
  4. Check for vulnerable sandbox patterns
    Review code that uses VM2's run, VM, or Sandbox classes to see if it processes external or user-supplied input without additional sanitization
    Affected if The application passes untrusted input to vm2 for execution within the sandbox

You are affected if vm2 version 3.9.10 or lower is installed as a dependency AND your application uses vm2 to run untrusted code.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.9.11 or later
Fixed in 3.9.11
Vendor patch github.com →
Interim mitigation

Upgrade vm2 to version 3.9.11 or later; there are no workarounds available for earlier versions.

Recommended fix High confidence

vm2 version 3.9.11

  1. 1. Identify all projects or dependencies that use the vm2 package with version less than 3.9.11 by running `npm list vm2` in project directories
  2. 2. Update package.json to specify vm2 version 3.9.11 or later (e.g., `"vm2": "^3.9.11"` or `"vm2": ">=3.9.11"`)
  3. 3. Run `npm install` or `npm update` to install the fixed version
  4. 4. Verify the installed version by running `npm list vm2` and confirming it shows version 3.9.11 or higher
  5. 5. Run any existing test suites to ensure the upgrade does not break functionality
  6. 6. Redeploy applications running this sandbox to production environments
Caveat Minor: Review release notes for 3.9.11 to confirm no breaking changes to your specific use case, though the vendor indicates no workarounds were available so upgrade should be safe

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vm2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,896.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-36067 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-36067 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data