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.
References
Link | Resource |
---|---|
https://nodesecurity.io/advisories/87 | Third Party Advisory |
https://github.com/hokaccha/node-jwt-simple/pull/16 | Issue Tracking Third Party Advisory |
https://github.com/hokaccha/node-jwt-simple/pull/14 | Issue Tracking Third Party Advisory |
https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/ | Broken Link Third Party Advisory |
Configurations
Information
Published : 2018-05-31 13:29
Updated : 2019-10-09 16:16
NVD link : CVE-2016-10555
Mitre link : CVE-2016-10555
JSON object : View
CWE
CWE-310
Cryptographic Issues
Products Affected
jwt-simple_project
- jwt-simple