ewxrjk sftpserver parse.c sftp_parse_path uninitialized pointer ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in ewxrjk sftpserver and classified as problematic. Affected by this vulnerability is the function sftp_parse_path of the file parse.c. This manipulation causes uninitialized pointer.
This vulnerability is registered as CVE-2020-36617. No exploit is available.
The presence of this vulnerability remains uncertain at this time.
Applying a patch is the recommended action to fix this issue.
In some deployment models this would be a vulnerability. README specifically warns about avoiding such deployment models.
Details
A vulnerability was found in ewxrjk sftpserver (the affected version unknown). It has been declared as problematic. Affected by this vulnerability is the function sftp_parse_path of the file parse.c. The manipulation with an unknown input leads to a uninitialized pointer vulnerability. The CWE definition for the vulnerability is CWE-824. The product accesses or uses a pointer that has not been initialized. The impact remains unknown.
The weakness was published 12/18/2022 as bf4032f34832ee11d79aa60a226cc018e7ec5eed. The advisory is shared at github.com. This vulnerability is known as CVE-2020-36617. Technical details are known, but no exploit is available.
The real existence of this vulnerability is still doubted at the moment. In some deployment models this would be a vulnerability. README specifically warns about avoiding such deployment models.
Applying the patch bf4032f34832ee11d79aa60a226cc018e7ec5eed is able to eliminate this problem. The bugfix is ready for download at github.com.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 4.6
CNA Vector (VulDB): 🔍
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: Uninitialized pointerCWE: CWE-824 / CWE-908
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: bf4032f34832ee11d79aa60a226cc018e7ec5eed
Timeline
12/18/2022 🔍12/18/2022 🔍
12/18/2022 🔍
08/04/2024 🔍
Sources
Product: github.comAdvisory: bf4032f34832ee11d79aa60a226cc018e7ec5eed
Status: Confirmed
Disputed: 🔍
CVE: CVE-2020-36617 (🔍)
GCVE (CVE): GCVE-0-2020-36617
GCVE (VulDB): GCVE-100-216205
Entry
Created: 12/18/2022 15:56Updated: 08/04/2024 20:36
Changes: 12/18/2022 15:56 (43), 01/15/2023 09:22 (2), 01/15/2023 09:27 (21), 08/04/2024 20:36 (15)
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.