-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Node Security Project advisory against ms package <=0.7.0 #2327
Comments
Hi! I think an issue has already been opened on this matter, and the package
Thanks for the report! Note: socket.io and socket.io-adapter will soon be released with that change included |
+1 |
Sorry about that then, I had a quick look through and a search and I didn't see anything about it... |
My +1 was ment for your post.
|
Any ETA for when a new release will be made with the fix? |
This has been updated but the version for socket.io itself hasn't been bumped and it hasn't been pushed to npm yet. On npm |
+1 |
@rauchg would you guys be able to do a patch release with |
Just released |
|
@rauchg thanks! |
@deansheather btw this hasn't updated on snyk yet, but I double checked the package.json files in question and I believe that resolves this issue. Thanks for the detailed analysis! |
No problem at all @mikermcneil! Could someone please close this issue now that this problem has been solved? |
The
ms
package which is included as a dependency 4 times when installing socket.io through thenpm install socket.io
command has been found to have a ReDoS vulnerability.The advisory can be found at Node Security Project. The advisory page contains proof of concept, results for the tests and methods to remediate this issue.
As you can see on the advisory page, to fix this vulnerability we would need to upgrade the dependencies for socket.io to use
ms
version 0.7.1 or greater OR limit the length of the input before passing it intoms
.I became aware of this issue after executing the
nsp check
command:You can confirm that socket.io is using
ms
version 0.6.2 by typingnpm ls
in your project directory.The text was updated successfully, but these errors were encountered: