Forgeable Public/Private Tokens in jws
Affected versions of the `jws` 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 as a bearer token, the end result is a complete authentication bypass with minimal effort. ## Recommendation Update to version 3.0.0 or later.
01
describes (1)
Related CVEs.
| ID | severity | exploitable |
|---|---|---|
| CVE-2016-1000223US | — | — |
02
references
External citations — patches, advisories, analysis.
- https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-librariesWEB
- https://github.com/brianloveswords/node-jwsPACKAGE
- https://github.com/brianloveswords/node-jws/commit/585d0e1e97b6747c10cf5b7689ccc5618a89b299#diff-4ac32a78649ca5bdd8e0ba38b7006a1eWEB
- https://nvd.nist.gov/vuln/detail/CVE-2016-1000223ADVISORY
- https://snyk.io/vuln/npm:jws:20160726WEB
- https://www.npmjs.com/advisories/88WEB
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