CVE-2016-10555 Forgeable Public/Private Tokens in jwt-simple
MediumCVSS 6.5
EPSS 4.7%
- Published
- Updated
- Exploit status
- No public exploit known
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 products
| Product | Affected versions | Fixed in |
|---|---|---|
| npm jwt-simple(npm) | < 0.3.1 | 0.3.1 |
| jwt-simple project jwt-simple | <= 0.3.0 | No fix listed |
| HackerOne jwt-simple node module | = <=0.3.0 | No fix listed |
References
- nvd.nist.gov third-party-advisory
- github.com issue-tracking patch third-party-advisory
- github.com patch
- www.npmjs.com
- github.com issue-tracking patch third-party-advisory
- auth0.com broken-link third-party-advisory
- github.com
- nodesecurity.io third-party-advisory