Gazie 7.32 /setup/install/setup.php hidden_req file access
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Gazie 7.32. This vulnerability affects unknown code of the file /setup/install/setup.php. This manipulation of the argument hidden_req as part of POST Parameter causes file access. This vulnerability appears as CVE-2020-12743. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability has been found in Gazie 7.32 and classified as critical. Affected by this vulnerability is some unknown processing of the file /setup/install/setup.php. The manipulation of the argument hidden_req as part of a POST Parameter leads to a file access vulnerability. The CWE definition for the vulnerability is CWE-552. The product makes files or directories accessible to unauthorized actors, even though they should not be. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in Gazie 7.32. A successful installation does not remove or block (or in any other way prevent use of) its own file /setup/install/setup.php, meaning that anyone can request it without authentication. This file allows arbitrary PHP file inclusion via a hidden_req POST parameter.
The weakness was presented 05/11/2020 (Website). The advisory is shared at sourceforge.net. This vulnerability is known as CVE-2020-12743 since 05/08/2020. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1083 for this issue.
By approaching the search of inurl:setup/install/setup.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
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
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: File accessCWE: CWE-552 / CWE-425
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
05/08/2020 🔍05/11/2020 🔍
05/12/2020 🔍
10/16/2020 🔍
Sources
Advisory: sourceforge.netStatus: Not defined
Confirmation: 🔍
CVE: CVE-2020-12743 (🔍)
GCVE (CVE): GCVE-0-2020-12743
GCVE (VulDB): GCVE-100-154993
Entry
Created: 05/12/2020 07:45Updated: 10/16/2020 14:10
Changes: 05/12/2020 07:45 (38), 05/12/2020 07:50 (17), 10/16/2020 14:10 (1)
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.