Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
CriticalPublic exploit

Sandbreak

IdentifiersCVE-2022-36067CWE-94

CVE-2022-36067 is a critical sandbox-escape vulnerability in the vm2 Node.js library, an open-source sandbox used to run untrusted JavaScript with restricted access to host resources. In affected versions prior to 3.9.11, a threat actor can bypass vm2 sandbox protections and escape the isolated execution context, resulting in remote code execution on the host running the sandbox. The provided content identifies this issue as a previously reported critical vm2 sandbox escape, codenamed "Sandbreak" by Oxeye researchers. Specific vulnerable functions or code paths are not provided in the supplied content.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to break out of the vm2 sandbox and execute arbitrary commands/code on the underlying host system. This fully undermines the trust boundary vm2 is intended to provide for untrusted code execution and can lead to complete compromise of the host process and potentially the broader system, depending on runtime privileges.

Mitigation

If you can’t patch tonight, do this now.

The provided content states there are no known workarounds. If immediate patching is not possible, the only practical risk-reduction measure is to avoid using vulnerable vm2 versions to execute untrusted code and to place such workloads behind stronger isolation boundaries external to vm2. However, no specific vendor-supported mitigation is provided in the supplied content.

Remediation

Patch, then assume compromise.

Upgrade vm2 to version 3.9.11 or later, as the vulnerability was patched in vm2 3.9.11 according to the provided content.
PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app
Exploit-For-CVE-2022-36067MaturityPoCVerified exploit

This repository provides a proof-of-concept exploit for CVE-2022-36067, a critical sandbox escape vulnerability in the vm2 Node.js module. The exploit leverages manipulation of the Error.prepareStackTrace property to break out of the vm2 sandbox and execute arbitrary OS commands via the child_process module. The main files are: - app.js: Demonstrates the exploit by running the payload in a vm2 VM context. - payload.js: Contains the actual payload code, which can be used to execute arbitrary commands by replacing the placeholder with the desired command. - package.json and package-lock.json: Define dependencies, notably vm2. To use the exploit, the attacker provides the payload (from payload.js) to a vulnerable application using vm2. If the application is vulnerable, arbitrary commands can be executed on the host. The exploit does not target a specific network endpoint but abuses the local Node.js environment. The repository is structured as a simple proof-of-concept for research and demonstration purposes.

PrathamrajgorDisclosed Nov 5, 2022javascriptjsonlocal
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Vm2 ProjectVm2application

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.