Nagios XI 2024R1.01 monitoringwizard.php sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Nagios XI 2024R1.01 and classified as critical. The impacted element is an unknown function of the file monitoringwizard.php. The manipulation leads to sql injection. This vulnerability is traded as CVE-2024-24401. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. The affected component should be upgraded.
Details
A vulnerability was found in Nagios XI 2024R1.01 (Log Management Software). It has been rated as critical. This issue affects an unknown part of the file monitoringwizard.php. The manipulation with an unknown input 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. The summary by CVE is:
SQL Injection vulnerability in Nagios XI 2024R1.01 allows a remote attacker to execute arbitrary code via a crafted payload to the monitoringwizard.php component.
The weakness was shared 02/26/2024. The advisory is shared at nagios.com. The identification of this vulnerability is CVE-2024-24401 since 01/25/2024. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.
The exploit is available at github.com. It is declared as proof-of-concept. By approaching the search of inurl:monitoringwizard.php it is possible to find vulnerable targets with Google Hacking.
Upgrading eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.7
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 9.8
CNA 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: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
01/25/2024 🔍02/26/2024 🔍
02/26/2024 🔍
08/30/2024 🔍
Sources
Advisory: nagios.comStatus: Confirmed
CVE: CVE-2024-24401 (🔍)
GCVE (CVE): GCVE-0-2024-24401
GCVE (VulDB): GCVE-100-254789
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 02/26/2024 19:27Updated: 08/30/2024 06:00
Changes: 02/26/2024 19:27 (40), 02/28/2024 00:03 (8), 08/30/2024 06:00 (27)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
https://www.linkedin.com/posts/jarod-jaslow-codename-mawk-265144201_cve-nagios-sqli-activity-7167991657559248896-S6AB