CVE-2023-2901710.0CriticalCWE-913

CVE-2023-29017: vm2 Sandbox Escape vulnerability

patriksimek · vm2

Affected: patriksimek vm2 · Exploitation: likely to be exploited (10% or more)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

63.2%probability of exploitation in the next 30 days

99th percentile

050100

Higher than 99% of scored CVEs

10.0CriticalCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

patriksimek · vm2< 3.9.15

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Likely to be exploited (10% or more). EPSS gives it a 10% or higher chance of exploitation in the next 30 days.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Improper Control of Dynamically-Managed Code Resources · Deserialization and Object Injection
Vendor: patriksimek
Published: April 2023
Band: Likely to be exploited (10% or more), April 2023

CoverageNo articles yet

No CyberSIXT article names CVE-2023-29017 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.