NATS nats-server up to 2.1.8 JWT Library null pointer dereference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in NATS nats-server up to 2.1.8. The affected element is an unknown function of the component JWT Library. Performing a manipulation results in null pointer dereference. This vulnerability is known as CVE-2020-26521. No exploit is available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in NATS nats-server up to 2.1.8. It has been classified as problematic. This affects an unknown functionality of the component JWT Library. The manipulation with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on availability.
The weakness was published 11/06/2020. The advisory is shared at openwall.com. This vulnerability is uniquely identified as CVE-2020-26521. Neither technical details nor an exploit are publicly available.
Upgrading to version 2.1.9 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
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: nats-server 2.1.9
Timeline
10/02/2020 🔍11/06/2020 🔍
11/06/2020 🔍
12/03/2020 🔍
Sources
Advisory: openwall.comStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2020-26521 (🔍)
GCVE (CVE): GCVE-0-2020-26521
GCVE (VulDB): GCVE-100-164445
Entry
Created: 11/06/2020 17:36Updated: 12/03/2020 11:19
Changes: 11/06/2020 17:36 (38), 12/03/2020 11:14 (3), 12/03/2020 11:19 (18)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.