CVE-2016-10555
MEDIUM 6.5EPSS 4.8%
Since "algorithm" isn't enforced in jwt.decode()in jwt-simple 0.3.0 and earlier, a malicious user could choose what algorithm is sent sent to the server. If the server is expecting RSA but is sent HMAC-SHA with RSA's public key, the server will think the public key is actually an HMAC private key. This could be used to forge any data an attacker wants.
- Affected
- HackerOne · jwt-simple node module
- CVSS v3.0 NVD
- 6.5 MEDIUM
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N - CVSS v2.0 NVD
- 4.0 MEDIUM
AV:N/AC:L/Au:S/C:N/I:P/A:N - EPSS
- 4.78% chance of exploitation in the next 30 days, 92nd percentile
- Published
- 2018-05-31
- Updated
- 2024-09-16
Proof-of-concept exploits (3)
- CircuitSoul/poc-cve-2016-105551★ · 2021-06-14
- FroydCod3r/poc-cve-2016-105551★ · 2021-06-14
- scent2d/PoC-CVE-2016-105550★ · 2022-01-03
Security advisories
- https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries
- hokaccha/node-jwt-simple/pull/14
- https://nodesecurity.io/advisories/87
- advisories/GHSA-vgrx-w6rg-8fqf