labstack echo on Windows Static File pathname traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in labstack echo on Windows. This affects an unknown function of the component Static File Handler. Performing a manipulation results in pathname traversal. This vulnerability is identified as CVE-2020-36565. There is not any exploit available. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability classified as problematic has been found in labstack echo on Windows (affected version not known). This affects some unknown functionality of the component Static File Handler. The manipulation with an unknown input leads to a pathname traversal vulnerability. CWE is classifying the issue as CWE-21. This is going to have an impact on confidentiality. The summary by CVE is:
Due to improper sanitization of user input on Windows, the static file handler 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 released 12/07/2022. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2020-36565 since 07/29/2022. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.
Applying the patch 4422e3b66b9fd498ed1ae1d0242d660d0ed3faaa is able to eliminate this problem. The bugfix is ready for download at github.com.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
License
Website
- Product: https://github.com/labstack/echo/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.3
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
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: 4422e3b66b9fd498ed1ae1d0242d660d0ed3faaa
Timeline
07/29/2022 🔍12/07/2022 🔍
12/07/2022 🔍
04/24/2025 🔍
Sources
Product: github.comAdvisory: 4422e3b66b9fd498ed1ae1d0242d660d0ed3faaa
Status: Confirmed
CVE: CVE-2020-36565 (🔍)
GCVE (CVE): GCVE-0-2020-36565
GCVE (VulDB): GCVE-100-215091
Entry
Created: 12/07/2022 20:28Updated: 04/24/2025 04:19
Changes: 12/07/2022 20:28 (41), 01/01/2023 10:25 (1), 01/01/2023 10:30 (11), 04/24/2025 04:19 (16)
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.