Back to Database
Status published
Medium
CVE-2016-10555
Since "algorithm" isn't enforced in jwt.decode()in jwt-simple 0.3.0 and earlier,...
Vulnerability Description
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.
Impact Analysis
Refer to official advisory for detailed impact metrics.
Remediation
Ensure systems are updated to the latest vendor-supplied patch levels.
THREAT MONITOR
Am I Vulnerable?
Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2016-10555
Credits & Attribution
No credits recorded in the NVD database.
References
More from HackerOne
View All →CVE-2018-3787
Path traversal in simplehttpserver <v0.2.1 allows listing any file on...
High
7.5
CVE-2018-3779
active-support ruby gem 5.2.0 could allow a remote attacker to...
Critical
9.8
CVE-2018-3778
Improper authorization in aedes version <0.35.0 will publish a LWT...
Medium
5.3
CVE-2018-3776
Improper input validator in Nextcloud Server prior to 12.0.3 and...
Medium
5.3
CVE-2018-3775
Improper Authentication in Nextcloud Server prior to version 12.0.3 would...
High
8.8
Affected Vendor
HackerOne
View all reports →Affected Software
jwt-simple node module
Vulnerable Versions:
<=0.3.0
Timeline
Official Publish:
May 31st, 2018
Last Modified:
September 16th, 2024
Added to House:
July 20th, 2026
CVSS Vectors
V3:
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N