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://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
Related Vulnerabilities
CVE-2017-16049 Vulnerability in npm package nodesqlite
CVE-2022-25349 Vulnerability in maven package org.webjars.npm:materialize-css
CVE-2019-10367 Vulnerability in maven package io.jenkins:configuration-as-code
CVE-2020-19698 Vulnerability in npm package editor.md
CVE-2019-1003024 Vulnerability in maven package org.jenkins-ci.plugins:script-security