-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
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
sec: critical vulnerability in transitive dep vm2 (via superagent-proxy) #380
Comments
We're keeping an eye on upstream for a fix for the moment. In the meantime, here's some information about Honeycomb's use of vm2:
What's This Mean For A Libhoney User?(according to our current understanding, confirmed upstream)
|
proxy-agent release 6.3.0 contains a fix in f1f3220d1. superagent-proxy's dependency on proxy-agent is currently |
## Which problem is this PR solving? - Resolves #380 ## Short description of the changes This is the equivalent behavior of the previous agent configuration. If a proxy URL is provided in libhoney config, a single ProxyAgent will be created with that proxy URL set for all connections. No nuanced lookup of proxy config from the environment based on target URL protocol. [proxy-agent is a hefty import](https://bundlephobia.com/package/[email protected]), but we were importing an early edition of it ([v5.0.0](https://bundlephobia.com/package/[email protected])) already via superagent-proxy. --------- Co-authored-by: JamieDanielson <[email protected]>
Versions
Description
In vm2 for versions up to 3.9.19, Promise handler sanitization can be bypassed, allowing attackers to escape the sandbox and run arbitrary code. The vm2 project alerts to the existence of critical security issues and claims to have been discontinued, therefore recommending replacing vm2 with isolated-vm.
The text was updated successfully, but these errors were encountered: