CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2016

CVE-2016-10555
Jwt-simple Project Jwt-simple vulnerability

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 products

Jwt-simple. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Jwt-simple Project Jwt-simple runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Set the orderSystems that can be reached from the internet come first, then the rest.

References

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.