Vulnerability record · CVE-2024-22120 · published 17 May 2024
CVE-2024-22120: Zabbix Server Audit Log clientip SQL Injection Enables Command Execution
Zabbix · Zabbix
Zabbix server fails to sanitize the clientip field before writing it to the audit log, allowing SQL injection into that field. Because the server can execute configured scripts, an attacker who can trigger an audit entry can chain the SQL injection into command execution. The flaw is a time-based blind SQL injection, so exploitation is possible without seeing query output.
Description
Zabbix server can perform command execution for configured scripts. After command is executed, audit entry is added to "Audit Log". Due to "clientip" field is not sanitized, it is possible to injection SQL into "clientip" and exploit time based blind SQL injection.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Automated analysis
high priorityHigh CVSS (8.8), very high EPSS and a vendor advisory tagged Exploit make this a likely target, though it requires low privileges and is not in KEV.
What it is
Zabbix server fails to sanitize the clientip field before writing it to the audit log, allowing SQL injection into that field. Because the server can execute configured scripts, an attacker who can trigger an audit entry can chain the SQL injection into command execution. The flaw is a time-based blind SQL injection, so exploitation is possible without seeing query output.
Impact
An attacker gains the ability to run commands through Zabbix's configured script execution and can read or alter database contents via blind SQL injection. CVSS 3.1 rates confidentiality, integrity and availability impact as high.
Attack surface
Reached over the network (AV:N) with low attack complexity and no user interaction. The vector requires low privileges (PR:L), so the attacker needs some authenticated access to the Zabbix server rather than being fully unauthenticated.
Exploitation
Not listed in CISA KEV, but EPSS is 0.76618 (99.5th percentile) and the vendor advisory is tagged Exploit, indicating public exploit material exists and exploitation is likely.
What to do
- Apply the Zabbix fix referenced in vendor advisory ZBX-24505 for the affected server version.
- Restrict network access to the Zabbix server and frontend to trusted management networks.
- Review and minimize accounts with privileges that can trigger script execution or audit log writes.
- Audit configured Zabbix scripts and disable any that are not required.
- Monitor Zabbix audit logs and database query behavior for anomalous clientip values.
Detection
- Inspect Zabbix audit log entries for clientip values containing SQL syntax, quotes, or time-delay functions.
- Alert on unusually long or repeated database queries originating from the Zabbix server process.
- Monitor for unexpected command execution spawned by the Zabbix server process.
- Correlate Zabbix audit log writes with subsequent script execution events.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| https://support.zabbix.com/browse/ZBX-24505 | ExploitVendor Advisory |
| https://support.zabbix.com/browse/ZBX-24505 | ExploitVendor Advisory |
Track CVE-2024-22120 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2024-22120), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.