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
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-for-github.aaakk.us.kgbot
changed the title
CVE-2022-23539 (Medium) detected in jsonwebtoken-0.4.0.tgz, jsonwebtoken-0.1.0.tgz
CVE-2022-23539 (High) detected in jsonwebtoken-0.4.0.tgz, jsonwebtoken-0.1.0.tgz
Jan 5, 2023
mend-for-github.aaakk.us.kgbot
changed the title
CVE-2022-23539 (High) detected in jsonwebtoken-0.4.0.tgz, jsonwebtoken-0.1.0.tgz
CVE-2022-23539 (Medium) detected in jsonwebtoken-0.4.0.tgz, jsonwebtoken-0.1.0.tgz
Jun 25, 2024
mend-for-github.aaakk.us.kgbot
changed the title
CVE-2022-23539 (Medium) detected in jsonwebtoken-0.4.0.tgz, jsonwebtoken-0.1.0.tgz
CVE-2022-23539 (High) detected in jsonwebtoken-0.4.0.tgz, jsonwebtoken-0.1.0.tgz
Jul 1, 2024
mend-for-github.aaakk.us.kgbot
changed the title
CVE-2022-23539 (High) detected in jsonwebtoken-0.4.0.tgz, jsonwebtoken-0.1.0.tgz
CVE-2022-23539 (Medium) detected in jsonwebtoken-0.4.0.tgz, jsonwebtoken-0.1.0.tgz
Sep 8, 2024
CVE-2022-23539 - Medium Severity Vulnerability
jsonwebtoken-0.4.0.tgz
JSON Web Token implementation (symmetric and asymmetric)
Library home page: https://registry.npmjs.org/jsonwebtoken/-/jsonwebtoken-0.4.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/jsonwebtoken/package.json
Dependency Hierarchy:
jsonwebtoken-0.1.0.tgz
JSON Web Token implementation (symmetric and asymmetric)
Library home page: https://registry.npmjs.org/jsonwebtoken/-/jsonwebtoken-0.1.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/express-jwt/node_modules/jsonwebtoken/package.json
Dependency Hierarchy:
Found in HEAD commit: ba236fd18ec3e6450d68d675bce1609d2e5d3230
Found in base branch: main
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-22
URL: CVE-2022-23539
Base Score Metrics:
Type: Upgrade version
Origin: GHSA-8cf7-32gw-wr33
Release Date: 2022-12-22
Fix Resolution (jsonwebtoken): 9.0.0
Direct dependency fix Resolution (express-jwt): 7.7.8
⛑️ Automatic Remediation will be attempted for this issue.
The text was updated successfully, but these errors were encountered: