CVE-2015-9235
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…
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (8.65%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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).
- CVSS 3.0
- 9.8 CRITICALCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 8.65% probability · 95th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-20, CWE-327
- Affected
- auth0/jsonwebtoken
- Source
- support@hackerone.com
References
- https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/Broken Link, Vendor Advisory
- https://github.com/auth0/node-jsonwebtoken/commit/1bb584bc382295eeb7ee8c4452a673a77a68b687Patch, Third Party Advisory
- https://nodesecurity.io/advisories/17Third Party Advisory
- https://www.timmclean.net/2015/02/25/jwt-alg-none.htmlExploit, Third Party Advisory
- https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/Broken Link, Vendor Advisory
- https://github.com/auth0/node-jsonwebtoken/commit/1bb584bc382295eeb7ee8c4452a673a77a68b687Patch, Third Party Advisory
- https://nodesecurity.io/advisories/17Third Party Advisory
- https://www.timmclean.net/2015/02/25/jwt-alg-none.htmlExploit, Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.