CVEvulnerability
CVE-2016-10555
6.5 MEDIUM
Official page ↗
- Status
- Modified
- Published
- 2018-05-31
- Last modified
- 2026-06-17
- Assigner
- [email protected]
- CVSS 3.0 ([email protected])
- 6.5 MEDIUM — CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
- CVSS 2.0 ([email protected])
- 4.0 MEDIUM — AV:N/AC:L/Au:S/C:N/I:P/A:N
- Weaknesses
- CWE-20, CWE-310
Description
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.
Affected configurations
• jwt-simple project jwt-simple (<= 0.3.0)
Related
Weakness · not in database (1)
Weakness · CWE (1)
- CWE-20 Improper Input Validation weakness
References
- https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/ Broken Link, Third Party Advisory
- https://github.com/hokaccha/node-jwt-simple/pull/14 Issue Tracking, Third Party Advisory
- https://github.com/hokaccha/node-jwt-simple/pull/16 Issue Tracking, Third Party Advisory
- https://nodesecurity.io/advisories/87 Third Party Advisory
- https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/ Broken Link, Third Party Advisory
- https://github.com/hokaccha/node-jwt-simple/pull/14 Issue Tracking, Third Party Advisory
- https://github.com/hokaccha/node-jwt-simple/pull/16 Issue Tracking, Third Party Advisory
- https://nodesecurity.io/advisories/87 Third Party Advisory