FusionPBX 4.5.7 app\edit\filerename.php folder/filename/newfilename pathname traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in FusionPBX 4.5.7. It has been rated as critical. The impacted element is an unknown function of the file app\edit\filerename.php. Performing a manipulation of the argument folder/filename/newfilename results in pathname traversal. This vulnerability was named CVE-2020-21055. There is no available exploit. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability, which was classified as critical, was found in FusionPBX 4.5.7. This affects an unknown function of the file app\edit\filerename.php. The manipulation of the argument folder/filename/newfilename 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, integrity, and availability.
The weakness was presented 05/21/2021. The advisory is shared at resp3ctblog.wordpress.com. This vulnerability is uniquely identified as CVE-2020-21055. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
By approaching the search of inurl:app\edit\filerename.php it is possible to find vulnerable targets with Google Hacking.
Applying a patch 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
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Partially
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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: github.com
Timeline
08/13/2020 🔍05/21/2021 🔍
05/21/2021 🔍
05/23/2021 🔍
Sources
Product: github.comAdvisory: resp3ctblog.wordpress.com
Status: Confirmed
CVE: CVE-2020-21055 (🔍)
GCVE (CVE): GCVE-0-2020-21055
GCVE (VulDB): GCVE-100-175413
Entry
Created: 05/21/2021 06:56Updated: 05/23/2021 08:40
Changes: 05/21/2021 06:56 (38), 05/23/2021 08:40 (5)
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.