Icinga Web 2 versions prior to 2.9.6 and 2.10 contain an information disclosure vulnerability that allows unauthenticated users to access arbitrary files on the local system that are accessible to the web-server user. This includes sensitive configuration files such as those containing database credentials.
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 (1 hidden).
This repository contains a single Metasploit auxiliary scanner module targeting a directory traversal vulnerability (CVE-2022-24716) in Icingaweb versions 2.8.0-2.8.5 and 2.9.0-2.9.5. The exploit leverages an unauthenticated HTTP GET request to the endpoint /lib/icinga/icinga-php-thirdparty/<absolute path to file> to retrieve arbitrary files from the server's filesystem as the web server user. The module allows the user to specify the target URI, port, and file to retrieve (defaulting to /etc/icinga2/icinga2.conf). The exploit is operational and can be used to exfiltrate sensitive files such as configuration files or /etc/passwd. The code is written in Ruby and is designed to be run within the Metasploit framework. No authentication is required on the target, and the attack vector is network-based. The repository is well-structured, containing only the 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.