jsonwebtoken-8.3.0.tgz: 3 vulnerabilities (highest severity is: 6.1) [master] #146
Description
📂 Vulnerable Library - jsonwebtoken-8.3.0.tgz
JSON Web Token implementation (symmetric and asymmetric)
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/jsonwebtoken/package.json
Findings
| Finding | Severity | 🎯 CVSS | Exploit Maturity | EPSS | Library | Type | Fixed in | Remediation Available | Reachability |
|---|---|---|---|---|---|---|---|---|---|
| CVE-2022-23540 | 🟠 Medium | 6.1 | Not Defined | < 1% | jsonwebtoken-8.3.0.tgz | Direct | jsonwebtoken - 9.0.0,jsonwebtoken - 9.0.0,jsonwebtoken - 9.0.0,https://github.com/auth0/node-jsonwebtoken.git - no_fix | ✅ | |
| CVE-2022-23539 | 🟠 Medium | 6.0 | Not Defined | < 1% | jsonwebtoken-8.3.0.tgz | Direct | https://github.com/auth0/node-jsonwebtoken.git - no_fix,jsonwebtoken - 9.0.0,jsonwebtoken - 9.0.0 | ✅ | |
| CVE-2022-23541 | 🟡 Low | 2.3 | Not Defined | < 1% | jsonwebtoken-8.3.0.tgz | Direct | jsonwebtoken - 9.0.0,jsonwebtoken - 9.0.0,https://github.com/auth0/node-jsonwebtoken.git - no_fix | ✅ |
Details
🟠CVE-2022-23540
Vulnerable Library - jsonwebtoken-8.3.0.tgz
JSON Web Token implementation (symmetric and asymmetric)
Library home page: https://registry.npmjs.org/jsonwebtoken/-/jsonwebtoken-8.3.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/jsonwebtoken/package.json
Dependency Hierarchy:
-
express-jwt-5.3.1.tgz (Root Library)
- ❌ jsonwebtoken-8.3.0.tgz (Vulnerable Library)
-
❌ jsonwebtoken-8.3.0.tgz (Vulnerable Library)
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: Dec 22, 2022 06:02 PM
URL: CVE-2022-23540
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 6.1
Suggested Fix
Type: Upgrade version
Origin: GHSA-qwph-4952-7xr6
Release Date: Dec 22, 2022 06:02 PM
Fix Resolution : jsonwebtoken - 9.0.0,jsonwebtoken - 9.0.0,jsonwebtoken - 9.0.0,https://github.com/auth0/node-jsonwebtoken.git - no_fix
🟠CVE-2022-23539
Vulnerable Library - jsonwebtoken-8.3.0.tgz
JSON Web Token implementation (symmetric and asymmetric)
Library home page: https://registry.npmjs.org/jsonwebtoken/-/jsonwebtoken-8.3.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/jsonwebtoken/package.json
Dependency Hierarchy:
-
express-jwt-5.3.1.tgz (Root Library)
- ❌ jsonwebtoken-8.3.0.tgz (Vulnerable Library)
-
❌ jsonwebtoken-8.3.0.tgz (Vulnerable Library)
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: Dec 22, 2022 11:20 PM
URL: CVE-2022-23539
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 6.0
Suggested Fix
Type: Upgrade version
Origin: https://osv.dev/vulnerability/CVE-2022-23539
Release Date: Dec 22, 2022 11:20 PM
Fix Resolution : https://github.com/auth0/node-jsonwebtoken.git - no_fix,jsonwebtoken - 9.0.0,jsonwebtoken - 9.0.0
🟡CVE-2022-23541
Vulnerable Library - jsonwebtoken-8.3.0.tgz
JSON Web Token implementation (symmetric and asymmetric)
Library home page: https://registry.npmjs.org/jsonwebtoken/-/jsonwebtoken-8.3.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/jsonwebtoken/package.json
Dependency Hierarchy:
-
express-jwt-5.3.1.tgz (Root Library)
- ❌ jsonwebtoken-8.3.0.tgz (Vulnerable Library)
-
❌ jsonwebtoken-8.3.0.tgz (Vulnerable Library)
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: Dec 22, 2022 05:52 PM
URL: CVE-2022-23541
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 2.3
Suggested Fix
Type: Upgrade version
Origin: GHSA-hjrf-2m68-5959
Release Date: Dec 22, 2022 05:52 PM
Fix Resolution : jsonwebtoken - 9.0.0,jsonwebtoken - 9.0.0,https://github.com/auth0/node-jsonwebtoken.git - no_fix