Verification Bypass in jsonwebtoken
Versions 4.2.1 and earlier of `jsonwebtoken` are affected by a verification bypass vulnerability. This is a result of weak validation of the JWT algorithm type, occuring when an attacker is allowed to arbitrarily specify the JWT algorithm. ## Recommendation Update to version 4.2.2 or later.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2015-9235US | critical9.8OT high | Exploit | ||
In jsonwebtoken node module before 4.2.2 it is possible for an attacker to bypass verification when a token digitally signed with an asymmetric key (RS/ES family) of algorithms but… | ||||
02
references
External citations — patches, advisories, analysis.
- https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-librariesWEB
- https://github.com/advisories/GHSA-c7hr-j4mj-j2w6ADVISORY
- https://github.com/auth0/node-jsonwebtoken/commit/1bb584bc382295eeb7ee8c4452a673a77a68b687WEB
- https://nvd.nist.gov/vuln/detail/CVE-2015-9235ADVISORY
- https://www.npmjs.com/advisories/17WEB
- https://www.timmclean.net/2015/02/25/jwt-alg-none.htmlWEB
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