CVE-2016-10555

moderate-risk
Published 2018-05-31

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.

Do I need to act?

!
81.7% chance of exploitation in next 30 days
EPSS score — higher than 18% of all CVEs
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
6
CVSS 6.5/10 Medium
NETWORK / LOW complexity

Affected Products (1)

Affected Vendors

Jwt-Simple Project

References (8)

Broken Link https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-lib...
Issue Tracking https://github.com/hokaccha/node-jwt-simple/pull/14
Issue Tracking https://github.com/hokaccha/node-jwt-simple/pull/16
Third Party Advisory https://nodesecurity.io/advisories/87
Broken Link https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-lib...
Issue Tracking https://github.com/hokaccha/node-jwt-simple/pull/14
Issue Tracking https://github.com/hokaccha/node-jwt-simple/pull/16
Third Party Advisory https://nodesecurity.io/advisories/87
49
/ 100
moderate-risk
Severity 24/34 · High
Exploitability 20/34 · Moderate
Exposure 5/34 · Minimal