CVSS 3.0
6.5 mediumCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:NCVE-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.
Severity
- EPSS
- 4.8% chance of exploitation in the next 30 days; higher than 91% of CVEs (scores of 2026-10-31)
- CWEs
- CWE-310, CWE-20
- Published
- Modified
- Record from
- the NVD, synced
Affected
- jwt-simple_project:jwt-simple
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-vgrx-w6rg-8fqf | npm | jwt-simple | <0.3.1 | 0.3.1 |
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/