CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
LOW
Integrity Impact
LOW
Availability Impact
LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
EPSS
Percentile
39.5%
Versions <=8.5.1
of jsonwebtoken
library can be misconfigured so that passing a poorly implemented key retrieval function (referring to the secretOrPublicKey
argument from the readme link) will result in incorrect verification of tokens. There is a possibility of using a different algorithm and key combination in verification than the one that was used to sign the tokens. Specifically, tokens signed with an asymmetric public key could be verified with a symmetric HS256 algorithm. This can lead to successful validation of forged tokens.
You will be affected if your application is supporting usage of both symmetric key and asymmetric key in jwt.verify() implementation with the same key retrieval function.
Update to version 9.0.0.
There is no impact for end users
Vendor | Product | Version | CPE |
---|---|---|---|
* | jsonwebtoken | * | cpe:2.3:a:*:jsonwebtoken:*:*:*:*:*:*:*:* |
github.com/advisories/GHSA-hjrf-2m68-5959
github.com/auth0/node-jsonwebtoken/commit/e1fa9dcc12054a8681db4e6373da1b30cf7016e3
github.com/auth0/node-jsonwebtoken/releases/tag/v9.0.0
github.com/auth0/node-jsonwebtoken/security/advisories/GHSA-hjrf-2m68-5959
nvd.nist.gov/vuln/detail/CVE-2022-23541
security.netapp.com/advisory/ntap-20240621-0007