jsonwebtoken-8.5.1.tgz: 3 vulnerabilities (highest severity is: 6.4)

[mend-bolt-for-github]

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: /api-gateway/package.json

Path to vulnerable library: /api-gateway/node_modules/jsonwebtoken/package.json,/token-incentive-system/node_modules/jsonwebtoken/package.json

Found in HEAD commit: a2ed13ef7f5dce613f19af695433a78d5b7ea082

Vulnerabilities

Vulnerability	Severity	CVSS	Dependency	Type	Fixed in (jsonwebtoken version)	Remediation Possible**
CVE-2022-23540	Medium	6.4	jsonwebtoken-8.5.1.tgz	Direct	9.0.0	❌
CVE-2022-23539	Medium	5.9	jsonwebtoken-8.5.1.tgz	Direct	9.0.0	❌
CVE-2022-23541	Medium	5.0	jsonwebtoken-8.5.1.tgz	Direct	N/A	❌

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2022-23540

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: /api-gateway/package.json

Path to vulnerable library: /api-gateway/node_modules/jsonwebtoken/package.json,/token-incentive-system/node_modules/jsonwebtoken/package.json

Dependency Hierarchy:

• ❌ jsonwebtoken-8.5.1.tgz (Vulnerable Library)

Found in HEAD commit: a2ed13ef7f5dce613f19af695433a78d5b7ea082

Found in base branch: main

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 Note: The description of this vulnerability differs from MITRE.

Publish Date: 2022-12-22

URL: CVE-2022-23540

CVSS 3 Score Details (6.4)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • 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: GHSA-qwph-4952-7xr6

Release Date: 2022-12-22

Fix Resolution: 9.0.0

Step up your Open Source Security Game with Mend here

CVE-2022-23539

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: /api-gateway/package.json

Path to vulnerable library: /api-gateway/node_modules/jsonwebtoken/package.json,/token-incentive-system/node_modules/jsonwebtoken/package.json

Dependency Hierarchy:

• ❌ jsonwebtoken-8.5.1.tgz (Vulnerable Library)

Found in HEAD commit: a2ed13ef7f5dce613f19af695433a78d5b7ea082

Found in base branch: main

Vulnerability Details

Versions "<=8.5.1" of "jsonwebtoken" library could be misconfigured so that legacy, insecure key types are used for signature verification. For example, DSA keys could be used with the RS256 algorithm. You are affected if you are using an algorithm and a key type other than a combination listed in the GitHub Security Advisory as unaffected. This issue has been fixed, please update to version 9.0.0. This version validates for asymmetric key type and algorithm combinations. Please refer to the above mentioned algorithm / key type combinations for the valid secure configuration. After updating to version 9.0.0, if you still intend to continue with signing or verifying tokens using invalid key type/algorithm value combinations, you’ll need to set the "allowInvalidAsymmetricKeyTypes" option to "true" in the "sign()" and/or "verify()" functions.
Mend Note: The description of this vulnerability differs from MITRE.

Publish Date: 2022-12-22

URL: CVE-2022-23539

CVSS 3 Score Details (5.9)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-8cf7-32gw-wr33

Release Date: 2022-12-22

Fix Resolution: 9.0.0

Step up your Open Source Security Game with Mend here

CVE-2022-23541

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: /api-gateway/package.json

Path to vulnerable library: /api-gateway/node_modules/jsonwebtoken/package.json,/token-incentive-system/node_modules/jsonwebtoken/package.json

Dependency Hierarchy:

• ❌ jsonwebtoken-8.5.1.tgz (Vulnerable Library)

Found in HEAD commit: a2ed13ef7f5dce613f19af695433a78d5b7ea082

Found in base branch: main

Vulnerability Details

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 Note: The description of this vulnerability differs from MITRE.

Publish Date: 2022-12-22

URL: CVE-2022-23541

CVSS 3 Score Details (5.0)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Step up your Open Source Security Game with Mend here