CVE-2023-29017criticalCWE-913

CVE-2023-29017: critical vulnerability in patriksimek vm2

vm2 Sandbox Escape vulnerability

Published · Updated

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

60Vexday Risk Score

Keep watching. It has a public proof of concept.

ssvc Attendcvss 10epss 63%
from disclosure to weapon1 day
Published on NVDApr 6
1st PoC+1d
What the vendors declare (VEX)

Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.

Affected
1 product
Red Hat Advanced Cluster Management for Kubernetes 2
workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
vm2 is a sandbox that can run untrusted code with whitelisted Node's built-in modules. Prior to version 3.9.15, vm2 was not properly handling host objects passed to `Error.prepareStackTrace` in case of unhandled async errors. A threat actor could 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.15 of vm2. There are no known workarounds.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Affected products
patriksimek · vm2
⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.