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).
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-c7hr-j4mj-j2w6 | Verification Bypass in jsonwebtoken |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Status: PUBLISHED
Assigner: hackerone
Published:
Updated: 2024-09-16T23:05:54.010Z
Reserved: 2017-10-29T00:00:00
Link: CVE-2015-9235
No data.
Status : Modified
Published: 2018-05-29T20:29:00.330
Modified: 2024-11-21T02:40:07.100
Link: CVE-2015-9235
OpenCVE Enrichment
No data.
Github GHSA