Loading vulnerability…
The node_process_command function in Zabbix Server before version 1.8 contains a vulnerability that allows remote attackers to execute arbitrary commands on the server. This is achieved by sending a specially crafted request to the vulnerable function, which fails to properly sanitize input before passing it to a command execution context.
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 module (modules/exploits/linux/misc/zabbix_server_exec.rb) that exploits an unauthenticated command execution vulnerability in Zabbix Server versions prior to 1.6.9 (tested on 1.6.7, CVE-2009-4498). The exploit abuses the 'Command' trap functionality in Zabbix's TCP protocol (default port 10051) to send arbitrary shell commands to the server. If the default Node ID (0) does not work, the module attempts to extract the correct Node ID from the server's error response and retries the attack. The payload is customizable via Metasploit and allows execution of arbitrary shell commands on the target system. The module is operational and provides remote command execution capabilities, but is not weaponized for mass exploitation. The only fingerprintable endpoint is the Zabbix server's TCP port 10051. The code is written in Ruby and is structured as a standard Metasploit exploit module.
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.