Cacti up to 1.2.6 Authorization graph_json.php local_graph_id authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Cacti up to 1.2.6. The affected element is an unknown function of the file graph_json.php of the component Authorization. Performing a manipulation of the argument local_graph_id as part of Parameter results in authorization. This vulnerability is reported as CVE-2019-16723. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as critical has been found in Cacti up to 1.2.6 (Log Management Software). This affects some unknown functionality of the file graph_json.php of the component Authorization. The manipulation of the argument local_graph_id as part of a Parameter leads to a authorization vulnerability. CWE is classifying the issue as CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In Cacti through 1.2.6, authenticated users may bypass authorization checks (for viewing a graph) via a direct graph_json.php request with a modified local_graph_id parameter.
The weakness was disclosed 09/23/2019 (Website). The advisory is shared at seclists.org. This vulnerability is uniquely identified as CVE-2019-16723 since 09/23/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. A authentication is required for exploitation. Technical details are known, but no exploit is available.
By approaching the search of inurl:graph_json.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
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.3
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: AuthorizationCWE: CWE-639 / CWE-285 / 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/23/2019 🔍09/23/2019 🔍
09/23/2019 🔍
12/27/2023 🔍
Sources
Advisory: 2964Status: Not defined
CVE: CVE-2019-16723 (🔍)
GCVE (CVE): GCVE-0-2019-16723
GCVE (VulDB): GCVE-100-142137
Entry
Created: 09/23/2019 20:59Updated: 12/27/2023 12:44
Changes: 09/23/2019 20:59 (56), 09/05/2020 09:55 (1), 12/27/2023 12:38 (3), 12/27/2023 12:44 (1)
Complete: 🔍
Cache ID: 216:1DC: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.