upgrading to proxy-agent 6.3 to avoid vulnerabilities#458
Open
DimejiFaluyi wants to merge 1 commit intogatsby-uc:masterfrom
Open
upgrading to proxy-agent 6.3 to avoid vulnerabilities#458DimejiFaluyi wants to merge 1 commit intogatsby-uc:masterfrom
DimejiFaluyi wants to merge 1 commit intogatsby-uc:masterfrom
Conversation
Author
|
@JoshuaWalsh tagging just in case. |
Author
|
tagging @jariz just in case as well |
|
@JoshuaWalsh / @jariz is this a change you could review? Updating proxy-agent would help get rid of a vulnerability in the dependency chain. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CVE-2023-37903
I would like to update to
proxy-agent 6.3to avoid a vuln around older versions ofproxy-agentthat usevm2which allows for Remote Code Execution.Background info:
vm2 is an open source vm/sandbox for Node.js. In vm2 for versions up to and including 3.9.19, Node.js custom inspect function allows attackers to escape the sandbox and run arbitrary code. This may result in Remote Code Execution, assuming the attacker has arbitrary code execution primitive inside the context of vm2 sandbox. There are no patches and no known workarounds. Users are advised to find an alternative software
I've linked the proxy-agent changelog here.