CVE-2016-10555

Jwt Simple vulnerability

CVSS

6.5

EPSS

4.9%

EPSS pct

91th

Exploited

No known

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 vendor

Jwt Simple Project

Affected product

Jwt Simple

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Weakness type (CWE)

CWE-20 — Improper Input Validation
CWE-310

Published

2018-05-31

Risk analysis

Based on its CVSS vector, this vulnerability is exploitable over the network, low attack complexity, requiring low privileges, no user interaction. Successful exploitation leads to high impact to integrity.

Its EPSS score of 4.9% reflects a lower probability of exploitation activity in the wild over the next 30 days, placing it above 91% of all scored CVEs.

Check your external exposure to CVE-2016-10555

Confirm whether Jwt Simple Project Jwt Simple is running on any internet-facing host or subdomain.
Match discovered service fingerprints against the version affected by CVE-2016-10555.
Prioritise remediation if the asset is public, business-critical, or near authentication/payment flows.

How ThreatPort helps with CVE-2016-10555

ThreatPort's external attack surface scanner checks your internet-facing assets — agentlessly, from the outside in — for the exposed services and versions that CVE-2016-10555 affects, then prioritises the finding by real risk using CISA KEV and FIRST.org EPSS.

Run a free external exposure scan

Are you exposed to CVE-2016-10555?

Run an instant, non-intrusive external scan to check your attack surface for CVE-2016-10555.

Start free scan

No credit card. Agentless.

Related vulnerabilities