Critical severity · published May 29, 2018
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…
9.8
CVSS
8.5%
EPSS
No
On KEV
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 vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)8.5% · higher than 95% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
JS
Jsonwebtoken · Auth0
before 4.2.2 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2015-9235
CVE.org
https://www.cve.org/CVERecord?id=CVE-2015-9235
Broken Link
https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/
Patch
https://github.com/auth0/node-jsonwebtoken/commit/1bb584bc382295eeb7ee8c4452a673a77a68b687
Third Party Advisory
https://nodesecurity.io/advisories/17
Exploit
https://www.timmclean.net/2015/02/25/jwt-alg-none.html
More from Jsonwebtoken
8.1
CVE-2022-23539
jsonwebtoken unrestricted key type could lead to legacy keys usage
7.6
CVE-2022-23540
jsonwebtoken vulnerable to signature validation bypass due to insecure default algorithm in jwt.verify()
6.3
CVE-2022-23541
jsonwebtoken's insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC