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.
No analysis available yet.
Remediation
No remediation available yet.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-vgrx-w6rg-8fqf | Forgeable Public/Private Tokens in jwt-simple |
References
History
Wed, 16 Jul 2025 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|
Status: PUBLISHED
Assigner: hackerone
Published:
Updated: 2024-09-16T16:38:09.923Z
Reserved: 2017-10-29T00:00:00.000Z
Link: CVE-2016-10555
No data.
Status : Modified
Published: 2018-05-31T20:29:02.067
Modified: 2024-11-21T02:44:16.137
Link: CVE-2016-10555
No data.
OpenCVE Enrichment
No data.
Github GHSA