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...
Vendor
jwt-simple project vulnerabilities
1 published CVE affecting jwt-simple project, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 1
- Critical
- 0
- High
- 0
- Medium
- 1
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Products
Latest jwt-simple project CVEs
Newest publication first
-
MediumCVSS 6.5 EPSS 4.7%
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.