Forgeable Public/Private Tokens in jws

published 2020-09-01 6y ago modified 2023-11-08 3y ago also GHSA-gjcw-v447-2w7q

cvss: 8.7; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no EPSS score yet
public exploits: 0; none known

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.

Patch / fix

fixed in 1 links 1

npm jws 3.0.0

github.com/brianloveswords/node-jws@585d0e1 commit

Is CVE-2016-1000223 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	8.7	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	jws	<3.0.0	3.0.0

References

Sources

GitHub Advisory GHSA-gjcw-v447-2w7q

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.