Loading vulnerability…
A command injection vulnerability exists in LibreNMS through version 1.47, specifically in html/includes/graphs/device/collectd.inc.php. User-supplied parameters are sanitized using mysqli_escape_real_string, which is intended for SQL injection prevention, not command-line argument sanitization. This allows an attacker to inject shell commands via unescaped characters (such as backticks) into the $rrd_cmd variable, which is subsequently executed with passthru().
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.
This repository contains a single Metasploit module: 'librenms_collectd_cmd_inject.rb', which exploits a command injection vulnerability (CVE-2019-10669) in the Collectd graphing functionality of LibreNMS (version 1.50 and below). The exploit works by injecting commands into the 'from' parameter of a GET request to 'graph.php', which is ultimately executed by the server due to improper sanitization. The module requires valid LibreNMS credentials and interacts with several endpoints to authenticate, enumerate devices, and identify a suitable Collectd plugin before delivering the payload. The default payload is a reverse shell, but any Metasploit command payload can be used. The code is written in Ruby and is fully integrated into the Metasploit framework, making it weaponized and easy to use for attackers. The attack vector is network-based, targeting the LibreNMS web interface over HTTP.
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.