Vulnerability Details CVE-2016-10555
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.
Exploit prediction scoring system (EPSS) score
EPSS Score 0.573
EPSS Ranking 98.0%
CVSS Severity
CVSS v3 Score 6.5
CVSS v2 Score 4.0
References
- https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/
- https://github.com/hokaccha/node-jwt-simple/pull/14
- https://github.com/hokaccha/node-jwt-simple/pull/16
- https://nodesecurity.io/advisories/87
- https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/
- https://github.com/hokaccha/node-jwt-simple/pull/14
- https://github.com/hokaccha/node-jwt-simple/pull/16
- https://nodesecurity.io/advisories/87
Products affected by CVE-2016-10555
-
cpe:2.3:a:jwt-simple_project:jwt-simple:0.1.0
-
cpe:2.3:a:jwt-simple_project:jwt-simple:0.2.0
-
cpe:2.3:a:jwt-simple_project:jwt-simple:0.3.0