Skip to content
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

Upgrade https-proxy-agent to version 2 #883

Merged
merged 2 commits into from
Apr 10, 2018

Conversation

kizzx2
Copy link
Contributor

@kizzx2 kizzx2 commented Apr 10, 2018

https-proxy-agent <= 2.1.1 (including 1.0.0) has a potential vulernability as documented in https://hackerone.com/reports/319532

https-proxy-agent <= 2.1.1 (including 1.0.0) has a potential vulernability as documented in https://hackerone.com/reports/319532
Copy link
Collaborator

@intelliot intelliot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

package.json Outdated
@@ -19,7 +19,7 @@
"@types/lodash": "^4.14.85",
"@types/ws": "^3.2.0",
"bignumber.js": "^4.1.0",
"https-proxy-agent": "^1.0.0",
"https-proxy-agent": "^2.0.0",
Copy link
Collaborator

@intelliot intelliot Apr 10, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like the vuln was fixed in 2.2.0. Can we make this "2.2.1" (no ^) to make sure we get the version we expect?

In light of #882 we'd like to use specific versions to reduce unpredictability.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, done

Copy link

@dappelt dappelt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@intelliot intelliot merged commit 9af3968 into XRPLF:develop Apr 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants