CVE-2016-10555

Published May 31, 2018 CVSS 3.0 · 6.5 Medium EPSS 4.7% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-vgrx-w6rg-8fqf Forgeable Public/Private Tokens in jwt-simple
History
Type Values Removed Values Added
Metrics epss

{'score': 0.71282}

epss

{'score': 0.71686}

Weaknesses

Sources

Status
PUBLISHED
Assigner
hackerone
Published
Updated
Sep 16, 2024, 4:38 PM
Reserved
Oct 29, 2017, 12:00 AM
Status
Modified
Published
May 31, 2018, 8:29 PM
Modified
Jun 17, 2026, 12:39 AM