BlackCat CMS 1.2.2 File Upload ajax_rename.php extension unrestricted upload
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in BlackCat CMS 1.2.2. It has been rated as critical. This affects an unknown part of the file backend\media\ajax_rename.php of the component File Upload. Performing a manipulation of the argument extension as part of Parameter results in unrestricted upload. This vulnerability is cataloged as CVE-2017-14399. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in BlackCat CMS 1.2.2 (Content Management System). It has been classified as critical. This affects an unknown function of the file backend\media\ajax_rename.php of the component File Upload. The manipulation of the argument extension as part of a Parameter leads to a unrestricted upload vulnerability. CWE is classifying the issue as CWE-434. The product allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In BlackCat CMS 1.2.2, unrestricted file upload is possible in backend\media\ajax_rename.php via the extension parameter, as demonstrated by changing the extension from .jpg to .php.
The bug was discovered 09/12/2017. The weakness was shared 09/12/2017 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2017-14399 since 09/12/2017. The exploitability is told to be easy. It is possible to initiate the attack remotely. The successful exploitation requires a authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1608.002 for this issue.
By approaching the search of inurl:backend\media\ajax_rename.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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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: Unrestricted uploadCWE: CWE-434 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
09/12/2017 🔍09/12/2017 🔍
09/12/2017 🔍
09/12/2017 🔍
09/13/2017 🔍
11/15/2019 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2017-14399 (🔍)
GCVE (CVE): GCVE-0-2017-14399
GCVE (VulDB): GCVE-100-106449
Entry
Created: 09/13/2017 11:02Updated: 11/15/2019 10:49
Changes: 09/13/2017 11:02 (53), 11/15/2019 10:49 (7)
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.