You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jsonwebtoken is an implementation of JSON Web Tokens. 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, other 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. If your application is supporting usage of both symmetric key and asymmetric key in jwt.verify() implementation with the same key retrieval function. This issue has been patched, please update to version 9.0.0.
mend-bolt-for-githubbot
changed the title
CVE-2022-23541 (Medium) detected in jsonwebtoken-8.5.1.tgz
CVE-2022-23541 (High) detected in jsonwebtoken-8.5.1.tgz
Jan 6, 2023
mend-bolt-for-githubbot
changed the title
CVE-2022-23541 (High) detected in jsonwebtoken-8.5.1.tgz
CVE-2022-23541 (Medium) detected in jsonwebtoken-8.5.1.tgz
Mar 17, 2023
CVE-2022-23541 - Medium Severity Vulnerability
Vulnerable Library - jsonwebtoken-8.5.1.tgz
JSON Web Token implementation (symmetric and asymmetric)
Library home page: https://registry.npmjs.org/jsonwebtoken/-/jsonwebtoken-8.5.1.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/@reactioncommerce/api-plugin-authentication/node_modules/jsonwebtoken/package.json
Dependency Hierarchy:
Found in HEAD commit: 565a18bfcb4225a6a89d4c12e34c894e523a58d7
Found in base branch: master
Vulnerability Details
jsonwebtoken is an implementation of JSON Web Tokens. Versions
<= 8.5.1
ofjsonwebtoken
library can be misconfigured so that passing a poorly implemented key retrieval function referring to thesecretOrPublicKey
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, other 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. If your application is supporting usage of both symmetric key and asymmetric key in jwt.verify() implementation with the same key retrieval function. This issue has been patched, please update to version 9.0.0.Publish Date: 2022-12-22
URL: CVE-2022-23541
CVSS 3 Score Details (6.3)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-hjrf-2m68-5959
Release Date: 2022-12-22
Fix Resolution: jsonwebtoken - 9.0.0
Step up your Open Source Security Game with Mend here
The text was updated successfully, but these errors were encountered: