Vulnerability Description
Since "algorithm" isn't enforced in jwt.decode()in jwt-simple 0.3.0 and earlier, a malicious user could choose what algorithm is sent sent to the server. If the server is expecting RSA but is sent HMAC-SHA with RSA's public key, the server will think the public key is actually an HMAC private key. This could be used to forge any data an attacker wants.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Jwt-Simple Project | Jwt-Simple | <= 0.3.0 |
Related Weaknesses (CWE)
References
- https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libBroken LinkThird Party Advisory
- https://github.com/hokaccha/node-jwt-simple/pull/14Issue TrackingThird Party Advisory
- https://github.com/hokaccha/node-jwt-simple/pull/16Issue TrackingThird Party Advisory
- https://nodesecurity.io/advisories/87Third Party Advisory
- https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libBroken LinkThird Party Advisory
- https://github.com/hokaccha/node-jwt-simple/pull/14Issue TrackingThird Party Advisory
- https://github.com/hokaccha/node-jwt-simple/pull/16Issue TrackingThird Party Advisory
- https://nodesecurity.io/advisories/87Third Party Advisory
FAQ
What is CVE-2016-10555?
CVE-2016-10555 is a vulnerability with a CVSS score of 6.5 (MEDIUM). Since "algorithm" isn't enforced in jwt.decode()in jwt-simple 0.3.0 and earlier, a malicious user could choose what algorithm is sent sent to the server. If the server is expecting RSA but is sent HMA...
How severe is CVE-2016-10555?
CVE-2016-10555 has been rated MEDIUM with a CVSS base score of 6.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2016-10555?
Check the references section above for vendor advisories and patch information. Affected products include: Jwt-Simple Project Jwt-Simple.