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.
Metrics
Affected Vendors & Products
References
History
No history.
MITRE
Status: PUBLISHED
Assigner: hackerone
Published: 2018-05-31T20:00:00Z
Updated: 2024-09-16T16:38:09.923Z
Reserved: 2017-10-29T00:00:00
Link: CVE-2016-10555
Vulnrichment
No data.
NVD
Status : Modified
Published: 2018-05-31T20:29:02.067
Modified: 2019-10-09T23:16:46.277
Link: CVE-2016-10555
Redhat
No data.