SQL Injection in Nagios XI admin/commandline.php
Nagios XI before version 5.4.13 contains a SQL injection vulnerability in the admin/commandline.php script, specifically in the handling of the 'cname' parameter. Unsanitized user input in this parameter is directly incorporated into SQL queries, allowing attackers to manipulate the database through crafted requests.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows an authenticated attacker to execute arbitrary SQL commands against the Nagios XI database. This can lead to data leakage, data modification, or potentially full compromise of the application depending on the database privileges of the web application.
If you can’t patch tonight, do this now.
Restrict access to the admin/commandline.php endpoint to trusted users only, and employ web application firewalls (WAFs) to detect and block SQL injection attempts as an interim measure until the application is patched.
Patch, then assume compromise.
Upgrade to Nagios XI version 5.4.13 or later, where proper input validation and parameterized queries are implemented to prevent SQL injection via the 'cname' parameter in admin/commandline.php.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.