Loading vulnerability…
CVE-2020-11800 is a remote code execution vulnerability in Zabbix Server versions 2.2.x, 3.0.x before 3.0.31, and 3.2. The vulnerability allows remote attackers to execute arbitrary code on the Zabbix Server, potentially compromising the entire monitoring infrastructure. The specific vulnerable function is not detailed, but the flaw exists in the server-side code handling remote requests.
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 is a small standalone proof-of-concept for CVE-2020-11800, a command injection flaw in Zabbix Server’s active proxy/auto-registration handling. The repo contains a vulnerable lab environment (Dockerfile and docker-compose.yml), a detailed README explaining setup and exploitation, and a short Python exploit script. The exploit is not part of a larger framework. The main exploit logic is in exploit.py. It opens a raw TCP connection to the target Zabbix server on port 10051, sends JSON messages, and first performs a fake agent registration using request="active checks", host="vulhub", and a malicious ip value of "ffff:::;touch /tmp/success2". This payload abuses insufficient validation of IPv6-like input so that when Zabbix later builds a shell command such as ping <host_ip>, the semicolon breaks out and executes an additional shell command. After registration, the script brute-forces host IDs from 10000 to 10499 by sending request="command" with scriptid=1 and varying hostid values, printing responses that do not contain 'failed'. This is intended to trigger the vulnerable execution path and identify the assigned host ID. Repository structure and purpose: Dockerfile builds a local image from vulhub/zabbix:3.0.3-server; docker-compose.yml defines a four-service lab (server, agent, mysql, web) exposing 10051 for the Zabbix server and 8080 for the web UI; README.md documents the vulnerability, root cause, exploitation flow, required Zabbix auto-registration configuration, and verification steps; exploit.py is the PoC entry point. Overall, the repository’s purpose is to reproduce and demonstrate remote command execution against vulnerable Zabbix Server 3.0.3 in a controlled Docker lab.
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.