Responsive Filemanager 9.13.1 upload.php url server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Responsive Filemanager 9.13.1. It has been classified as critical. Impacted is an unknown function of the file upload.php. Performing a manipulation of the argument url as part of Parameter results in server-side request forgery. This vulnerability is cataloged as CVE-2018-14728. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.
Details
A vulnerability classified as critical has been found in Responsive Filemanager 9.13.1. This affects an unknown code block of the file upload.php. The manipulation of the argument url as part of a Parameter leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
upload.php in Responsive FileManager 9.13.1 allows SSRF via the url parameter.
The bug was discovered 07/29/2018. The weakness was shared 08/03/2018 (Website). The advisory is shared at packetstormsecurity.com. This vulnerability is uniquely identified as CVE-2018-14728 since 07/28/2018. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 5 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:upload.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Exploit-DB (45103). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 6.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Server-side request forgeryCWE: CWE-918
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/28/2018 🔍07/29/2018 🔍
08/03/2018 🔍
08/03/2018 🔍
08/04/2018 🔍
06/22/2024 🔍
Sources
Advisory: 148742Status: Not defined
CVE: CVE-2018-14728 (🔍)
GCVE (CVE): GCVE-0-2018-14728
GCVE (VulDB): GCVE-100-122589
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/04/2018 08:24Updated: 06/22/2024 10:58
Changes: 08/04/2018 08:24 (59), 03/13/2020 09:37 (4), 04/29/2023 14:38 (4), 06/22/2024 10:58 (14)
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.