CVE-2015-9235
high-risk
Published 2018-05-29
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).
Do I need to act?
!
32.5% chance of exploitation in next 30 days
EPSS score — higher than 68% of all CVEs
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
9
CVSS 9.8/10
Critical
NETWORK
/ LOW complexity
Affected Products (1)
Jsonwebtoken
Affected Vendors
References (8)
Third Party Advisory
https://nodesecurity.io/advisories/17
Third Party Advisory
https://nodesecurity.io/advisories/17
53
/ 100
high-risk
Severity
32/34 · Critical
Exploitability
16/34 · Moderate
Exposure
5/34 · Minimal