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 version of request library to fix vulnerability #188

Closed
clementallen opened this issue Mar 23, 2018 · 8 comments
Closed

Upgrade version of request library to fix vulnerability #188

clementallen opened this issue Mar 23, 2018 · 8 comments

Comments

@clementallen
Copy link

The current version of the request library uses a version of tough-cookie which has a security vulnerability. Upgrading request would mean this vulnerable version would no longer be used.

Vulnerability:
https://www.versioneye.com/Node.JS/tough-cookie/2.3.2

Fix in request:
request/request#2776

@clementallen clementallen changed the title Upgrade version of request library Upgrade version of request library to fix vulnerability Mar 23, 2018
@delucis
Copy link

delucis commented Apr 26, 2018

The current version of request also depends on an old and vulnerable hoek (via hawk).

Vulnerability:
https://nvd.nist.gov/vuln/detail/CVE-2018-3728

@epheph
Copy link

epheph commented Apr 26, 2018

#189

@davedoesdev
Copy link

Re the hoak vulnerability.
node-coveralls brings in hoak 4.2.1 which is not vulnerable:

https://nodesecurity.io/advisories/566
hapijs/hoek#230

@delucis
Copy link

delucis commented Apr 26, 2018

My bad, double checked and as far as I can tell, it is indeed bringing in 4.2.1.

@epheph
Copy link

epheph commented Apr 26, 2018

It could end up using a lower version of hoek if there's another old request/hoek elsewhere in your project (like babel-cli)

@davedoesdev
Copy link

IMHO that's a problem with the project depending on an older request/hoek.

request 3.0.0 depends on request ^2.79.0 so is happy to accept patches to the 2.x.x line.

@davedoesdev
Copy link

I think this is fixed now, thanks

@nickmerwin
Copy link
Owner

Thanks!

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

No branches or pull requests

5 participants