Loading vulnerability…
Nagios versions prior to 3.1.1 contain a command injection vulnerability in the statuswml.cgi script. The vulnerability arises because the script fails to properly sanitize user-supplied input in the 'ping' and 'Traceroute' parameters, allowing attackers to inject arbitrary shell metacharacters. This can result in the execution of arbitrary commands on the server with the privileges of the web server process.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
This repository contains a single Metasploit module: 'Nagios3 statuswml.cgi Ping Command Execution'. The module exploits a metacharacter injection vulnerability (CVE-2009-2288) in the Nagios3 statuswml.cgi script, allowing remote attackers to execute arbitrary shell commands via the 'ping' parameter. The exploit works by sending a crafted HTTP POST request to the CGI script, authenticating with provided credentials, and injecting the payload as a shell command. The module is written in Ruby and leverages Metasploit's HttpClient mixin. The only required endpoint is the path to the vulnerable CGI script, typically '/nagios3/cgi-bin/statuswml.cgi'. The exploit is operational, providing command execution on the target system if successful. The repository is structured as a single Metasploit exploit module file.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.