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

dependency on "ws" version < 2.00 has security flaw in random number generator #538

Closed
1 of 2 tasks
pmuellr opened this issue Feb 10, 2017 · 5 comments
Closed
1 of 2 tasks

Comments

@pmuellr
Copy link

pmuellr commented Feb 10, 2017

Note: for support questions, please use one of these channels: stackoverflow or slack

You want to:

  • report a bug
  • request a feature

Current behaviour

Fails vulnerability test with snyk vuln db.

See same issue on engine.io - socketio/engine.io#479

Steps to reproduce (if the current behaviour is a bug)

Expected behaviour

Setup

  • OS:
  • browser:
  • engine.io version:

Other information (e.g. stacktraces, related issues, suggestions how to fix)

@darrachequesne
Copy link
Member

I'll be happy to merge your pull request 👍

@pmuellr
Copy link
Author

pmuellr commented Feb 14, 2017

Will do, if I find the time. Need to investigate what the ws upgrade entails.

Breaking changes from ws 1.x -> 2.x are listed here: https://github.com/websockets/ws/releases/tag/2.0.0

Complete changelog for ws here: https://github.com/websockets/ws/releases

I guess the first step is to run the tests ...

Also looks like ws 1.1.2 might have patched the vulnerability, so that would be an easier upgrade - but Snyk has not yet marked this as "not vulnerable" yet - https://snyk.io/vuln/npm:ws:20160920

@mrvini
Copy link

mrvini commented Feb 15, 2017

@darrachequesne, is there a plan to upgrade engine.io-client to most recent version of WS

pmuellr pushed a commit to pmuellr/engine.io-client that referenced this issue Feb 16, 2017
fixes: socketio#538
'dependency on "ws" version < 2.00 has security flaw in random
number generator'
@pmuellr
Copy link
Author

pmuellr commented Feb 16, 2017

Note that my snyk vuln checking tool doesn't flag ws 1.1.2 as a vulnerability as of today, unlike when it did yesterday. They updated the vulnerable version expression to < 1.1.2.

Submitted PR #540 for this, I suspect more testing will be required.

@darrachequesne
Copy link
Member

Closed by #539.

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 a pull request may close this issue.

3 participants