CVE-2015-9235: Use of a Broken or Risky Cryptographic Algorithm
(updated )
In jsonwebtoken node module before 4.2.2 it is possible for an attacker to bypass verification when a token digitally signed with an asymmetric key (RS/ES family) of algorithms but instead the attacker send a token digitally signed with a symmetric algorithm (HS* family).
References
- auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/
- github.com/advisories/GHSA-c7hr-j4mj-j2w6
- github.com/auth0/node-jsonwebtoken/commit/1bb584bc382295eeb7ee8c4452a673a77a68b687
- nodesecurity.io/advisories/17
- nvd.nist.gov/vuln/detail/CVE-2015-9235
- www.npmjs.com/advisories/17
- www.timmclean.net/2015/02/25/jwt-alg-none.html
Code Behaviors & Features
Detect and mitigate CVE-2015-9235 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →