{"id":"EUVD-2018-0569","enisaUuid":"e63fa433-f8c6-3916-9489-47c0cea6ee81","description":"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).","datePublished":"May 29, 2018, 8:00:00 PM","dateUpdated":"Sep 16, 2024, 11:05:54 PM","baseScore":null,"references":"https://nodesecurity.io/advisories/17\nhttps://github.com/auth0/node-jsonwebtoken/commit/1bb584bc382295eeb7ee8c4452a673a77a68b687\nhttps://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/\nhttps://www.timmclean.net/2015/02/25/jwt-alg-none.html\n","aliases":"CVE-2015-9235\nGHSA-c7hr-j4mj-j2w6\n","assigner":"hackerone","epss":8.37,"enisaIdProduct":[{"id":"bd1b0491-ae01-3d65-8f23-ec5f4100a846","product":{"name":"jsonwebtoken node module","vendor":{"name":"HackerOne"}},"product_version":"\u003c4.2.2"}],"enisaIdVendor":[{"id":"e1a51d5d-cb49-3646-80cf-ec27769c8f4d","vendor":{"name":"HackerOne"}}],"enisaIdVulnerability":[{"id":"3ae0c11c-1804-35e7-8684-2ab5cf8370c7","vulnerability":{"id":"GHSA-c7hr-j4mj-j2w6","description":"Verification Bypass in jsonwebtoken","datePublished":"Oct 9, 2018, 12:38:30 AM","dateUpdated":"Aug 31, 2020, 6:07:57 PM","baseScore":null,"references":"https://nvd.nist.gov/vuln/detail/CVE-2015-9235\nhttps://github.com/auth0/node-jsonwebtoken/commit/1bb584bc382295eeb7ee8c4452a673a77a68b687\nhttps://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries\nhttps://github.com/advisories/GHSA-c7hr-j4mj-j2w6\nhttps://www.npmjs.com/advisories/17\nhttps://www.timmclean.net/2015/02/25/jwt-alg-none.html\n","enisa_id":"EUVD-2018-0569\n","aliases":"GHSA-c7hr-j4mj-j2w6\nCVE-2015-9235\n","epss":0.0,"dataProcessed":"Nov 15, 2026, 2:05:47 AM","vulnerabilityProduct":[],"vulnerabilityVendor":[]}},{"id":"efc865fd-688b-3344-8251-599858370819","vulnerability":{"id":"CVE-2015-9235","description":"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).","datePublished":"May 29, 2018, 8:00:00 PM","dateUpdated":"Sep 16, 2024, 11:05:54 PM","status":"PUBLISHED","baseScore":null,"references":"https://nodesecurity.io/advisories/17\nhttps://github.com/auth0/node-jsonwebtoken/commit/1bb584bc382295eeb7ee8c4452a673a77a68b687\nhttps://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/\nhttps://www.timmclean.net/2015/02/25/jwt-alg-none.html\n","enisa_id":"EUVD-2018-0569\n","assigner":"hackerone","epss":8.37,"dataProcessed":"Nov 16, 2026, 7:23:53 AM","vulnerabilityProduct":[{"id":"6ea48569-1f26-3f61-a379-d1a79bf4ef69","product":{"name":"jsonwebtoken node module","vendor":{"name":"HackerOne"}},"product_version":"\u003c4.2.2"}],"vulnerabilityVendor":[{"id":"46f9c234-c35a-3f9d-82d9-d8123959a039","vendor":{"name":"HackerOne"}}]}}],"enisaIdAdvisory":[]}