CVE-2016-10555

https://notcve.org/view.php?id=CVE-2016-10555

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 servidor. Si el servidor espera RSA pero recibe HMAC-SHA con la clave pública RSA, el servidor pensará que la clave pública es, en realidad, una clave privada HMAC. • https://github.com/thepcn3rd/jwtToken-CVE-2016-10555 https://github.com/scent2d/PoC-CVE-2016-10555 https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries https://github.com/hokaccha/node-jwt-simple/pull/14 https://github.com/hokaccha/node-jwt-simple/pull/16 https://nodesecurity.io/advisories/87 • CWE-20: Improper Input Validation CWE-310: Cryptographic Issues •