jsonwebtoken up to 8.5.1 Public/Private improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in jsonwebtoken up to 8.5.1. It has been classified as critical. This affects an unknown part of the file Public/Private. The manipulation leads to improper authentication. This vulnerability is referenced as CVE-2022-23541. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as critical, has been found in jsonwebtoken up to 8.5.1. This issue affects an unknown code block of the file Public/Private. The manipulation with an unknown input leads to a improper authentication vulnerability. Using CWE to declare the problem leads to CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Impacted is confidentiality, integrity, and availability.
The weakness was published 12/22/2022. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2022-23541 since 01/19/2022. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 9.0.0 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.0VulDB Meta Temp Score: 6.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 5.0
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: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
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: jsonwebtoken 9.0.0
Patch: github.com
Timeline
01/19/2022 🔍12/22/2022 🔍
12/22/2022 🔍
01/22/2023 🔍
Sources
Advisory: e1fa9dcc12054a8681db4e6373da1b30cf7016e3Status: Confirmed
CVE: CVE-2022-23541 (🔍)
GCVE (CVE): GCVE-0-2022-23541
GCVE (VulDB): GCVE-100-216515
Entry
Created: 12/22/2022 09:07Updated: 01/22/2023 10:11
Changes: 12/22/2022 09:07 (38), 01/22/2023 10:06 (4), 01/22/2023 10:11 (21)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.