node-jsonwebtoken up to 8.5.1 jwt.verify secretOrPublicKey input validation
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
8.2 | $0-$5k | 0.00 |
A vulnerability was found in node-jsonwebtoken up to 8.5.1. It has been declared as critical. Affected by this vulnerability is the function jwt.verify
. The manipulation of the argument secretOrPublicKey
with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was released 12/22/2022 as GHSA-27h2-hvpr-p74q. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2022-23529 since 01/19/2022. Technical details of the vulnerability are known, but there is no available exploit.
The real existence of this vulnerability is still doubted at the moment.
Upgrading to version 9.0.0 eliminates this vulnerability. Applying the patch e1fa9dcc12054a8681db4e6373da1b30cf7016e3 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.3VulDB Meta Temp Score: 8.2
VulDB Base Score: 7.6
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 7.6
CNA Vector (GitHub, Inc.): 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: node-jsonwebtoken 9.0.0
Patch: e1fa9dcc12054a8681db4e6373da1b30cf7016e3
Timeline
01/19/2022 🔍12/22/2022 🔍
12/22/2022 🔍
01/22/2023 🔍
Sources
Advisory: GHSA-27h2-hvpr-p74qStatus: Confirmed
Disputed: 🔍
CVE: CVE-2022-23529 (🔍)
Entry
Created: 12/22/2022 08:52Updated: 01/22/2023 10:02
Changes: 12/22/2022 08:52 (52), 01/10/2023 16:43 (2), 01/22/2023 10:02 (11)
Complete: 🔍
No comments yet. Languages: en.
Please log in to comment.