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.
Configurations

Configuration 1 (hide)

cpe:2.3:a:jwt-simple_project:jwt-simple:*:*:*:*:*:node.js:*:*

History

21 Nov 2024, 02:44

Type Values Removed Values Added
References () https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/ - Broken Link, Third Party Advisory () https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/ - Broken Link, Third Party Advisory
References () https://github.com/hokaccha/node-jwt-simple/pull/14 - Issue Tracking, Third Party Advisory () https://github.com/hokaccha/node-jwt-simple/pull/14 - Issue Tracking, Third Party Advisory
References () https://github.com/hokaccha/node-jwt-simple/pull/16 - Issue Tracking, Third Party Advisory () https://github.com/hokaccha/node-jwt-simple/pull/16 - Issue Tracking, Third Party Advisory
References () https://nodesecurity.io/advisories/87 - Third Party Advisory () https://nodesecurity.io/advisories/87 - Third Party Advisory

Information

Published : 2018-05-31 20:29

Updated : 2024-11-21 02:44


NVD link : CVE-2016-10555

Mitre link : CVE-2016-10555

CVE.ORG link : CVE-2016-10555


JSON object : View

Products Affected

jwt-simple_project

  • jwt-simple
CWE
CWE-20

Improper Input Validation

CWE-310

Cryptographic Issues