-
Notifications
You must be signed in to change notification settings - Fork 518
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
[vulnerabilities][high] jsonwebtoken has insecure input validation in jwt.verify function #846
Comments
twilio-node v3 supports Node v6/8/10 which are not supported by jsonwebtoken v9. But, after reviewing the vulnerabilities in jsonwebtoken v8, our helper lib is not affected (we don’t verify signatures, only do the signing, and we use default algorithms) so no action is planned. We have a twilio-node v4 release candidate available here https://github.com/twilio/twilio-node/tree/4.0.0-rc which drops support for Node < v14 (since v14 is the oldest maintained Node version right now). I’ll update the PR to upgrade jsonwebtoken to v9 for the v4 release candidate anyway. |
Relates to #846 and #847 twilio-node v3 supports Node v6/8/10 which are not supported by jsonwebtoken v9. But, after reviewing the vulnerabilities in jsonwebtoken v8, our helper lib is not affected (we don’t verify signatures, only do the signing, and we use default algorithms). This change is to bypass audit failures for v3. Note that v4 does not bypass the audit and uses jsonwebtoken v9.
Relates to #846 and #847 twilio-node v3 supports Node v6/8/10 which are not supported by jsonwebtoken v9. But, after reviewing the vulnerabilities in jsonwebtoken v8, our helper lib is not affected (we don’t verify signatures, only do the signing, and we use default algorithms). This change is to bypass audit failures for v3. Note that v4 does not bypass the audit and uses jsonwebtoken v9.
Hey @childish-sambino, Thanks for closing this high vulnerability, but from what we understand, the fix is currently available only for twilio-node v4. I have a couple of questions regarding the above,
Thanks in advance. |
From what I understand starting with version 4 it has been decided to drop support for node versions < 14. |
If you are on node 12, so you cannot update twilio to 14, but you are able to update jsonwebtoken to 9 use this: https://github.com/rogeriochaves/npm-force-resolutions to force jsonwebtoken to be 9.0.0 for now. Looking at the code, it will not break (did not try out though). Since Node 12 LTS already ended I doubt that twilio will provide a node 12 compatible package with jsonwebtoken updated to 9. |
@uri-peled-unit We are planning to roll out GA on Jan 25. Subject to change |
Note that modern version of "overrides": {
"jsonwebtoken": "^9.0.0"
}, I must say, though, this is far from ideal. I think |
New jsonwebtoken vulnerability has been published.
GHSA-27h2-hvpr-p74q
The text was updated successfully, but these errors were encountered: