| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in go-aah. This impacts the function HTTPEngine.Handle. The manipulation leads to pathname traversal.
This vulnerability is traded as CVE-2020-36559. There is no exploit available.
It is suggested to install a patch to address this issue.
Details
A vulnerability, which was classified as problematic, has been found in go-aah (version now known). This issue affects the function HTTPEngine.Handle. The manipulation with an unknown input leads to a pathname traversal vulnerability. Using CWE to declare the problem leads to CWE-21. Impacted is confidentiality. The summary by CVE is:
Due to improper santization of user input, HTTPEngine.Handle allows for directory traversal, allowing an attacker to read files outside of the target directory that the server has permission to read.
The weakness was shared 12/28/2022 as 266. The advisory is shared at github.com. The identification of this vulnerability is CVE-2020-36559 since 07/29/2022. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
Applying the patch 881dc9f71d1f7a4e8a9a39df9c5c081d3a2da1ec is able to eliminate this problem. The bugfix is ready for download at github.com.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
License
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: 🔍
Exploiting
Class: Pathname traversalCWE: CWE-21 / CWE-22
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: 881dc9f71d1f7a4e8a9a39df9c5c081d3a2da1ec
Timeline
07/29/2022 🔍12/28/2022 🔍
12/28/2022 🔍
04/11/2025 🔍
Sources
Advisory: 266Status: Confirmed
CVE: CVE-2020-36559 (🔍)
GCVE (CVE): GCVE-0-2020-36559
GCVE (VulDB): GCVE-100-216929
Entry
Created: 12/28/2022 09:19Updated: 04/11/2025 19:34
Changes: 12/28/2022 09:19 (40), 01/25/2023 12:36 (11), 04/11/2025 19:34 (16)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.