{"url":"http://public2.vulnerablecode.io/api/packages/52946?format=json","purl":"pkg:npm/jwt-simple@0.0.0","type":"npm","namespace":"","name":"jwt-simple","version":"0.0.0","qualifiers":{},"subpath":"","is_vulnerable":true,"next_non_vulnerable_version":"0.5.3","latest_non_vulnerable_version":"0.5.3","affected_by_vulnerabilities":[{"url":"http://public2.vulnerablecode.io/api/vulnerabilities/38241?format=json","vulnerability_id":"VCID-q6zc-zwaf-3bcu","summary":"Forgeable Public/Private Tokens\nSince `algorithm` isn't enforced in `jwt.decode()`, 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.","references":[{"reference_url":"https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/","reference_id":"","reference_type":"","scores":[],"url":"https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/"},{"reference_url":"https://github.com/hokaccha/node-jwt-simple/pull/14","reference_id":"","reference_type":"","scores":[],"url":"https://github.com/hokaccha/node-jwt-simple/pull/14"},{"reference_url":"https://github.com/hokaccha/node-jwt-simple/pull/16","reference_id":"","reference_type":"","scores":[],"url":"https://github.com/hokaccha/node-jwt-simple/pull/16"}],"fixed_packages":[],"aliases":["GMS-2016-79"],"risk_score":null,"exploitability":"0.5","weighted_severity":"0.0","resource_url":"http://public2.vulnerablecode.io/vulnerabilities/VCID-q6zc-zwaf-3bcu"}],"fixing_vulnerabilities":[],"risk_score":null,"resource_url":"http://public2.vulnerablecode.io/packages/pkg:npm/jwt-simple@0.0.0"}