reportdata Module up to 3.4 on MunkiReport reportdata_controller.php req sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in reportdata Module up to 3.4 on MunkiReport. It has been declared as critical. This impacts an unknown function of the file reportdata_controller.php. Such manipulation of the argument req as part of Parameter leads to sql injection. This vulnerability is listed as CVE-2020-15886. The attack may be performed from remote. There is no available exploit. It is recommended to upgrade the affected component.
Details
A vulnerability was found in reportdata Module up to 3.4 on MunkiReport (Reporting Software). It has been rated as critical. Affected by this issue is some unknown processing of the file reportdata_controller.php. The manipulation of the argument req as part of a Parameter leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. CVE summarizes:
A SQL injection vulnerability in reportdata_controller.php in the reportdata module before 3.5 for MunkiReport allows attackers to execute arbitrary SQL commands via the req parameter of the /module/reportdata/ip endpoint.
The weakness was presented 07/23/2020. This vulnerability is handled as CVE-2020-15886 since 07/21/2020. The attack may be launched remotely. Required for exploitation is a simple authentication. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1505.
By approaching the search of inurl:reportdata_controller.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 3.5 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
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: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: reportdata Module 3.5
Timeline
07/21/2020 🔍07/23/2020 🔍
07/24/2020 🔍
07/24/2020 🔍
Sources
Status: Not definedCVE: CVE-2020-15886 (🔍)
GCVE (CVE): GCVE-0-2020-15886
GCVE (VulDB): GCVE-100-158948
Entry
Created: 07/24/2020 09:22Updated: 07/24/2020 09:27
Changes: 07/24/2020 09:22 (39), 07/24/2020 09:27 (18)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.