UniSharp laravel-filemanager up to 2.5.1 download working_dir pathname traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in UniSharp laravel-filemanager up to 2.5.1 and classified as critical. This affects an unknown part of the file Download. Performing a manipulation of the argument working_dir results in pathname traversal. This vulnerability is reported as CVE-2022-40734. No exploit exists.
Details
A vulnerability was found in UniSharp laravel-filemanager up to 2.5.1. It has been classified as problematic. This affects an unknown part of the file download. The manipulation of the argument working_dir 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:
UniSharp laravel-filemanager (aka Laravel Filemanager) through 2.5.1 allows download?working_dir=%2F.. directory traversal to read arbitrary files, as exploited in the wild in June 2022.
The weakness was disclosed 09/15/2022 as 1150. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2022-40734 since 09/14/2022. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 5.0
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
09/14/2022 🔍09/15/2022 🔍
09/15/2022 🔍
10/17/2022 🔍
Sources
Product: github.comAdvisory: 1150
Status: Confirmed
CVE: CVE-2022-40734 (🔍)
GCVE (CVE): GCVE-0-2022-40734
GCVE (VulDB): GCVE-100-208617
Entry
Created: 09/15/2022 07:28Updated: 10/17/2022 14:39
Changes: 09/15/2022 07:28 (40), 10/17/2022 14:39 (11)
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.