Loading vulnerability…
CVE-2022-23134 is an authorization flaw in the Zabbix Frontend setup workflow. After initial deployment, when the frontend configuration exists, portions of the setup process remain accessible to unauthenticated users rather than being restricted to super-administrators. An attacker can pass setup-step validation checks and potentially modify Zabbix Frontend configuration.
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 provides a proof-of-concept (POC) exploit and a detailed writeup for CVE-2022-23134, an authentication bypass vulnerability in Zabbix PHP frontend versions 5.4.0 to 5.4.8RC1 and certain 6.0.0 pre-releases. The exploit (exploit.py) is a Python script that crafts a malicious base64-encoded 'zbx_session' cookie containing attacker-controlled MySQL database connection parameters. It sends this cookie in a POST request to the vulnerable Zabbix 'setup.php' endpoint, tricking Zabbix into connecting to the attacker's database and granting privileged access. The script requires the attacker to have a prepared MySQL server and knowledge of the target's setup.php URL. The repository also includes a comprehensive writeup (writeup.md) explaining the vulnerability, setup requirements, and exploitation process. No detection scripts or fake code are present; the exploit is functional but does not provide direct code execution, only privileged access to the Zabbix instance.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.