CVE-2016-10555
N/A
N/A
Summary
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 Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| HackerOne | jwt-simple node module | <=0.3.0 | affected |
Weaknesses
- CWE-20: Improper Input Validation (CWE-20)
ADP Enrichment
CVE Program Container
Additional References
- https://nodesecurity.io/advisories/87
- https://github.com/hokaccha/node-jwt-simple/pull/14
- https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/
- https://github.com/hokaccha/node-jwt-simple/pull/16
References
- https://nodesecurity.io/advisories/87
- https://github.com/hokaccha/node-jwt-simple/pull/14
- https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/
- https://github.com/hokaccha/node-jwt-simple/pull/16
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.