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
Path to dependency file: /core/jazz_cognito-admin-authorizer/package.json
Path to vulnerable library: /core/jazz_cognito-admin-authorizer/node_modules/jsonwebtoken/package.json,/core/jazz_cognito-authorizer/node_modules/jsonwebtoken/package.json,/core/jazz_token-authorizer/node_modules/jsonwebtoken/package.json
Dependency Hierarchy:
❌ jsonwebtoken-7.4.3.tgz (Vulnerable Library)
Found in base branch: develop
Vulnerability Details
In versions <=8.5.1 of jsonwebtoken library, lack of algorithm definition in the jwt.verify() function can lead to signature validation bypass due to defaulting to the none algorithm for signature verification. Users are affected if you do not specify algorithms in the jwt.verify() function. This issue has been fixed, please update to version 9.0.0 which removes the default support for the none algorithm in the jwt.verify() method. There will be no impact, if you update to version 9.0.0 and you don’t need to allow for the none algorithm. If you need 'none' algorithm, you have to explicitly specify that in jwt.verify() options.
mend-for-github-combot
changed the title
CVE-2022-23540 (High) detected in jsonwebtoken-7.4.3.tgz
CVE-2022-23540 (Medium) detected in jsonwebtoken-7.4.3.tgz
Sep 8, 2024
CVE-2022-23540 - Medium Severity Vulnerability
Vulnerable Library - jsonwebtoken-7.4.3.tgz
JSON Web Token implementation (symmetric and asymmetric)
Library home page: https://registry.npmjs.org/jsonwebtoken/-/jsonwebtoken-7.4.3.tgz
Path to dependency file: /core/jazz_cognito-admin-authorizer/package.json
Path to vulnerable library: /core/jazz_cognito-admin-authorizer/node_modules/jsonwebtoken/package.json,/core/jazz_cognito-authorizer/node_modules/jsonwebtoken/package.json,/core/jazz_token-authorizer/node_modules/jsonwebtoken/package.json
Dependency Hierarchy:
Found in base branch: develop
Vulnerability Details
In versions
<=8.5.1
ofjsonwebtoken
library, lack of algorithm definition in thejwt.verify()
function can lead to signature validation bypass due to defaulting to thenone
algorithm for signature verification. Users are affected if you do not specify algorithms in thejwt.verify()
function. This issue has been fixed, please update to version 9.0.0 which removes the default support for the none algorithm in thejwt.verify()
method. There will be no impact, if you update to version 9.0.0 and you don’t need to allow for thenone
algorithm. If you need 'none' algorithm, you have to explicitly specify that injwt.verify()
options.Publish Date: 2022-12-22
URL: CVE-2022-23540
CVSS 3 Score Details (6.4)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://www.cve.org/CVERecord?id=CVE-2022-23540
Release Date: 2022-12-22
Fix Resolution: 9.0.0
The text was updated successfully, but these errors were encountered: