Loading HuntDB...

CVE-2016-10555

UNKNOWN
Published 2018-05-31T20:00:00Z
Actions:

Expert Analysis

Professional remediation guidance

Get tailored security recommendations from our analyst team for CVE-2016-10555. We'll provide specific mitigation strategies based on your environment and risk profile.

No CVSS data available

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.

Available Exploits

No exploits available for this CVE.

Related News

No news articles found for this CVE.

Affected Products

GitHub Security Advisories

Community-driven vulnerability intelligence from GitHub

✓ GitHub Reviewed CRITICAL

Forgeable Public/Private Tokens in jwt-simple

GHSA-vgrx-w6rg-8fqf

Advisory Details

Affected versions of the `jwt-simple` package allow users to select what algorithm the server will use to verify a provided JWT. A malicious actor can use this behaviour to arbitrarily modify the contents of a JWT while still passing verification. For the common use case of the JWT, the end result is a complete authentication bypass with minimal effort. ## Recommendation Update to version 0.3.1 or later. Additionally, be sure to always specify an algorithm in calls to `.decode()`.

Affected Packages

npm jwt-simple
ECOSYSTEM: ≥0 <0.3.1

CVSS Scoring

CVSS Score

9.0

Advisory provided by GitHub Security Advisory Database. Published: November 6, 2018, Modified: August 31, 2020

References

Published: 2018-05-31T20:00:00Z
Last Modified: 2024-09-16T16:38:09.923Z
Copied to clipboard!