{"uuid": "a90e6aa9-3ebe-43d6-9d13-4e73ff62eab3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-36067", "type": "seen", "source": "https://t.me/hacking_Attack/72607", "content": "Black Hat Ethical Hacking\nCritical RCE Vulnerability Found in vm2 Sandbox Library\n\nCritical RCE Vulnerability Found in vm2 Sandbox LibraryPost Views: 1 Premium Contenthttps://www.blackhatethicalhacking.com/wp-content/uploads/2022/09/Patreon.png Subscribe to Patreon to watch this episode.\nReading Time: 3 Minutes Researchers are warning of a critical remote code execution flaw in \u2018vm2\u2019, a JavaScript sandbox library downloaded over 16 million times per month via the NPM package repository.The vm2 vulnerability is tracked as CVE-2022-36067 and received a severity rating of 10.0, the maximum score in the CVSS system, as it could allow attackers to escape the sandbox environment and run commands on a host system.\n\nSandboxes are meant to be an isolated environment that is walled off from the rest of the operating system. However, as developers commonly use sandboxes to run or test potentially unsafe code, the ability to \u201cescape\u201d from this confined environment and execute code on the host is a massive security problem.\nSee Also: So you want to be a hacker? Complete Offensive Security and Ethical Hacking Course Escaping the sandboxSecurity researchers at Oxeye have found a clever way to customize the call stack of an error that occurs in VM2 to generate \u201cCallSite\u201d objects created outside the sandbox and use them to access Node\u2019s global objects and execute commands.\n\nWhile the library\u2019s authors attempted to mitigate this possibility in the past, Oxeye\u2019s researchers found a way to bypass this mitigation mechanism by using a custom implementation of the \u201cprepareStackTrace\u201d method.\n\n\u201cThe reporter\u2019s POC bypassed the logic above since vm2 missed wrapping specific methods related to the \u201cWeakMap\u201d JavaScript built-in type,\u201d the researchers explain in their report. \n\n\u201cThis allowed the attacker to provide their own implementation of \u201cprepareStackTrace,\u201d then trigger an error, and escape the sandbox.\u201d\nhttps://www.bleepstatic.com/images/news/u/1220909/Diagrams/sandbox-escape-process.png \nUpdate as soon as possibleOxeye\u2019s research team discovered this critical problem on August 16, 2022, and reported it to the VM2 team a couple of days later, who confirmed they had launched an investigation.\n\nEventually, the authors of the popular library released version 3.9.11 on August 28, 2022, which addressed the sandbox escape and code execution problems.\n\nSoftware developers are urged to update to the latest VM2 version and replace older releases in their projects as soon as possible.\n\nFor end users, it is important to note that it could take a while before virtualization software tools relying on VM2 apply the available security update.\n\nAs we saw with Log4Shell, a critical security problem in a widely deployed open-source library may persist for extended periods without the impacted users even knowing they\u2019re vulnerable due to the obscurity in the supply chain.\n\nIf you use a sandbox solution, check if it relies on VM2 and whether it\u2019s using the latest version.\nTrending: Microsoft SQL servers hacked with FARGO ransomware attacks Are u a security researcher? Or a company that writes articles or write ups about Cyber Security, Offensive Secur[...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-02T01:01:35.509951Z"}