1 results (0.006 seconds)

CVSS: 6.5EPSS: 58%CPEs: 1EXPL: 4

31 May 2018 — 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. Como "algorithm" no se aplica en jwt.decode() en jwt-simple en versiones 0.3.0 y anteriores, un usuario malicioso podría elegir qué algoritmo se envía al ser... • https://github.com/thepcn3rd/jwtToken-CVE-2016-10555 • CWE-20: Improper Input Validation CWE-310: Cryptographic Issues •