This repository was archived by the owner on May 5, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 68
Critical security vulnerability in vm2 #74
Comments
Same here, happily looking for this to be fixed. |
Looks like it is resolved, as well as CVE-2022-36067
|
@alasdairhurst Not sure how you are getting that vm2 version but it does not appear to be directly from proxy-agent@5.0.0 EDIT: ah for some reason I had to delete my package-lock.json and now its picking up vm2@3.9.11 |
3.9.11 is also now a vulnerable version, should now be upgraded to 3.9.17 |
This code in this repository has been moved to the |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Sandbox bypass in vm2 - GHSA-6pw2-5hjv-9pf7
fix available via
npm audit fix
node_modules/vm2
1 critical severity vulnerability
npm list vm2 shows this repository as part of the dependency chain
Connects to: TooTallNate/node-pac-proxy-agent#46
The text was updated successfully, but these errors were encountered: