We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In vm2 for versions up to 3.9.19, Node.js custom inspect function allows attackers to escape the sandbox and run arbitrary code.
Impact Remote Code Execution, assuming the attacker has arbitrary code execution primitive inside the context of vm2 sandbox.
Patches None.
Workarounds None.
References PoC is to be disclosed on or after the 5th of September.
Similarity with CVE-2023-37466 While this advisory might look similar to CVE-2023-37466, it is a completely different way of escaping the sandbox.
For more information If you have any questions or comments about this advisory:
Open an issue in VM2 Thanks to Xion (SeungHyun Lee) of KAIST Hacking Lab for disclosing this vulnerability.
The text was updated successfully, but these errors were encountered:
Maybe you should have a look at #533
Sorry, something went wrong.
No branches or pull requests
I have received GitHub Dependabot notifications for my project.
In vm2 for versions up to 3.9.19, Node.js custom inspect function allows attackers to escape the sandbox and run arbitrary code.
Impact
Remote Code Execution, assuming the attacker has arbitrary code execution primitive inside the context of vm2 sandbox.
Patches
None.
Workarounds
None.
References
PoC is to be disclosed on or after the 5th of September.
Similarity with CVE-2023-37466
While this advisory might look similar to CVE-2023-37466, it is a completely different way of escaping the sandbox.
For more information
If you have any questions or comments about this advisory:
Open an issue in VM2
Thanks to Xion (SeungHyun Lee) of KAIST Hacking Lab for disclosing this vulnerability.
The text was updated successfully, but these errors were encountered: