Forgeable Public/Private Tokens in jwt-simple
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()`.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2016-10555US | medium6.5 | Exploit | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-librariesWEB
- https://github.com/hokaccha/node-jwt-simple/commit/957957cfa44474049b4603b293569588ee9ffd97WEB
- https://github.com/hokaccha/node-jwt-simple/pull/14WEB
- https://github.com/hokaccha/node-jwt-simple/pull/16WEB
- https://nvd.nist.gov/vuln/detail/CVE-2016-10555ADVISORY
- https://www.npmjs.com/advisories/87WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan