-
-
Notifications
You must be signed in to change notification settings - Fork 727
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
Update QS as it vulnerable #229
Update QS as it vulnerable #229
Comments
We don't use the part of the qs module that has the vulnerability, so it is not necessary to update for any protection. We will however release an update regardless. |
I thought I released this last week, but from that link:
What the fuck. It's basically impossible not to play release a new version with an updated qs game. |
May use another module with more specific functionality? |
If you know one, please let me know and I'd be happy to switch :) I'm not aware of any so we will completely drop the qs module and thus extended urlencoded parsing in 2.0 |
haha, of course Coveralls.io decides to change the way it reports coverage... |
Published to npm as 1.17.1 |
Express also related to this module, updated to 4.15.2. Thanks. |
No problem. Express is also not actually affected either, as it also does not use the vulnerable functionality from Qs. |
https://snyk.io/vuln/npm:qs:20170213
The text was updated successfully, but these errors were encountered: