CVE-2022-23540 (High) detected in jsonwebtoken-7.4.3.tgz - autoclosed

[mend-for-github-com]

CVE-2022-23540 - High 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:

• ❌ jsonwebtoken-7.4.3.tgz (Vulnerable Library)

Found in HEAD commit: 712665b267203375ee4b15e1f8d1ebe08abc1547

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.

Publish Date: 2022-12-22

URL: CVE-2022-23540

CVSS 3 Score Details (7.6)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: Low
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: Low
  • Integrity Impact: High
  • Availability Impact: Low

For more information on CVSS3 Scores, click here.

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

---

⛑️ Automatic Remediation will be attempted for this issue.

[mend-for-github-com]

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[mend-for-github-com]

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.

[mend-for-github-com]

ℹ️ This issue was automatically closed by Mend because it is a duplicate of an existing issue: #395