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
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the section "Details" below to see if there is a version of transitive dependency where vulnerability is fixed.
Path to vulnerable library: /node_modules/jsonwebtoken/package.json
Dependency Hierarchy:
octokit-2.0.10.tgz (Root Library)
app-13.0.11.tgz
auth-app-4.0.7.tgz
universal-github-app-jwt-1.1.0.tgz
❌ jsonwebtoken-8.5.1.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
node-jsonwebtoken is a JsonWebToken implementation for node.js. For versions <= 8.5.1 of jsonwebtoken library, if a malicious actor has the ability to modify the key retrieval parameter (referring to the secretOrPublicKey argument from the readme link of the jwt.verify() function, they can write arbitrary files on the host machine. Users are affected only if untrusted entities are allowed to modify the key retrieval parameter of the jwt.verify() on a host that you control. This issue has been fixed, please update to version 9.0.0.
Path to vulnerable library: /node_modules/jsonwebtoken/package.json
Dependency Hierarchy:
octokit-2.0.10.tgz (Root Library)
app-13.0.11.tgz
auth-app-4.0.7.tgz
universal-github-app-jwt-1.1.0.tgz
❌ jsonwebtoken-8.5.1.tgz (Vulnerable Library)
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-bolt-for-githubbot
changed the title
octokit-2.0.10.tgz: 1 vulnerabilities (highest severity is: 7.6)
octokit-2.0.10.tgz: 2 vulnerabilities (highest severity is: 7.6)
Dec 24, 2022
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/jsonwebtoken/package.json
Vulnerabilities
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the section "Details" below to see if there is a version of transitive dependency where vulnerability is fixed.
Details
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/jsonwebtoken/package.json
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
node-jsonwebtoken is a JsonWebToken implementation for node.js. For versions
<= 8.5.1
ofjsonwebtoken
library, if a malicious actor has the ability to modify the key retrieval parameter (referring to thesecretOrPublicKey
argument from the readme link of thejwt.verify()
function, they can write arbitrary files on the host machine. Users are affected only if untrusted entities are allowed to modify the key retrieval parameter of thejwt.verify()
on a host that you control. This issue has been fixed, please update to version 9.0.0.Publish Date: 2022-12-21
URL: CVE-2022-23529
CVSS 3 Score Details (7.6)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-27h2-hvpr-p74q
Release Date: 2022-12-21
Fix Resolution: jsonwebtoken - 9.0.0
Step up your Open Source Security Game with Mend here
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/jsonwebtoken/package.json
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
Versions
<=8.5.1
ofjsonwebtoken
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 theallowInvalidAsymmetricKeyTypes
option totrue
in thesign()
and/orverify()
functions.Publish Date: 2022-12-23
URL: CVE-2022-23539
CVSS 3 Score Details (5.9)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-8cf7-32gw-wr33
Release Date: 2022-12-23
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: