CVE-2016-10555
Medium
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.
SeverityMedium
CVSS6.5
Exploit probability—
ProductJwt-simple
PublishedMay 31, 2018
First seenMay 31, 2018
Weakness typeCWE-20Improper input validation
How to fix
Update
- jwt-simple0.3.1 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| jwt-simple_project jwt-simple | v ≤ 0.3.0 | — |
| jwt-simplenpm | v < 0.3.1 | 0.3.1 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
In the Intelligence 360 plan
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.