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.
Remediation
References
https://nodesecurity.io/advisories/87
https://github.com/hokaccha/node-jwt-simple/pull/16
https://github.com/hokaccha/node-jwt-simple/pull/14
https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/
Related Vulnerabilities
CVE-2022-31193 Vulnerability in maven package org.dspace:dspace-jspui
CVE-2019-16567 Vulnerability in maven package org.jenkins-ci.plugins:teamconcert
CVE-2022-24728 Vulnerability in maven package org.webjars.bowergithub.ckeditor:ckeditor4
CVE-2020-17516 Vulnerability in maven package org.apache.cassandra:cassandra-all
CVE-2018-1000096 Vulnerability in npm package tiny-json-http