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

13 vulnerabilities found in 59 packages #3464

Closed
stuk88 opened this issue Jan 5, 2016 · 14 comments
Closed

13 vulnerabilities found in 59 packages #3464

stuk88 opened this issue Jan 5, 2016 · 14 comments
Labels

Comments

@stuk88
Copy link

stuk88 commented Jan 5, 2016

Snyk test report for sails found 13 vulnerabilities found in 59 packages
https://snyk.io/test/npm/sails

@sgress454
Copy link
Member

This is awesome, thanks! We'll run it on the upcoming v0.12.x release, I think some of these issues have been fixed (the Express version, for example).

@mikermcneil
Copy link
Member

@stuk88 Thanks for posting. If we're able to isolate any of these issues in 0.11, we'll also release a patch. For future reference, please review our vulnerability disclosure guide for the appropriate way of reporting a suspected security issue.

@mikermcneil
Copy link
Member

Ok, so Socket.io 1.4.0 which was just released fixes two of these issues: socketio/socket.io#2327 (comment)

@mikermcneil
Copy link
Member

If express-handlebars is not upgraded in the next couple of days (see ericf/express-handlebars#142 (comment)), we'll include a conditional warning in core that displays if you're using handlebars about that potential vulnerability.

@RWOverdijk
Copy link
Contributor

Well done :)

@sgress454
Copy link
Member

I added a warning that displays if you're using handlebars < 4. If/when express-handlebars update drops, the warning should go away after the end user does an npm update. ff56838

@sgress454
Copy link
Member

Ok, v0.11.4 is out which addresses most of the vulnerabilities. The only relevant remaining ones are express-handlebars and sails-hook-sockets, because the socket.io-client update failed to update the underlying engine.io dependency. Once that gets done, I'll bump sails-hook-sockets again. Unfortunately the 1.3.7->1.4.0 update had some breaking changes for us that have been fixed, but it means that to play on the safe side I had to peg the versions at 1.4.0. So, when the next update to socket.io-client comes out I'll bump the version in sails-hook-sockets again, and all should be right with the world. Whew.

The remaining vulnerabilities don't have direct remedies, but they also only affect grunt, so they should never be an issue in a production environment.

@mikermcneil
Copy link
Member

👍 @sgress454 💧 ⚡

To add a bit more color: As @sgress454 pointed out, with the exception of the socket.io-client thing (which @rauchg is on top of) the remaining vulnerabilities not addressed by 0.11.4 are from grunt-contrib-watch (which is only used in development) and express-handlebars (for which we've added a warning).

I'll leave this issue open until the socket.io-client dep is updated (we'll just need to make a change to the generator).

@stuk88 thanks again!

@jasalazar
Copy link

Hello everyone, i am starting the Sails way and it's awesome!

How can i update to this release on my current Sails project?

Thanks a lot!

@mikermcneil
Copy link
Member

@jasalazar you can update by running npm install sails@latest --force --save. Hope that helps!

@mikermcneil mikermcneil added the bug label Jan 8, 2016
@mikermcneil
Copy link
Member

Update: Guillermo patched socket.io-client and socket.io for everyone last night. We'll bump the generators today, and the do another patch to sails-hook-sockets to bump the deps once we've had a chance to do some more in-depth testing (likely tomorrow or Monday -- the only thing that will be affected in the mean time are the integration tests therein)

@mikermcneil
Copy link
Member

@sgress454
Copy link
Member

We're all set with sails-hook-sockets, sails.io.js and sails-generate-sails.io.js updated to use the latest versions of socket.io and socket.io-client (v1.4.3). I've left the dependencies as ~1.4.3 ranges in case any more updates are pushed out. Thanks everyone for the support on this! We're subscribed to the Github issue for the express-handlebars update, so when that's patched (hopefully soon) we'll be notified and will be able to update Sails accordingly.

@mikermcneil
Copy link
Member

We're subscribed to the Github issue for the express-handlebars update, so when that's patched (hopefully soon) we'll be notified and will be able to update Sails accordingly.

To add to this, the express-handlebars dependency is only actually used in Sails core if you change the default view engine from ejs to handlebars (it's included to make it easier for folks using handlebars to take advantage of layouts and partials).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

5 participants