CVE-2024-22120
Published: 17 May 2024
Summary
CVE-2024-22120 is a critical-severity Improper Input Validation (CWE-20) vulnerability in Zabbix Zabbix. Its CVSS base score is 9.1 (Critical).
Operationally, ranked in the top 0.3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
Zabbix server is affected by an input sanitization flaw in its audit logging mechanism for script command execution. When a configured script runs, an audit entry is written that includes an unsanitized "clientip" field; this permits an attacker to inject SQL and trigger a time-based blind SQL injection vulnerability.
An authenticated user with administrative privileges can exploit the issue over the network to execute arbitrary SQL commands against the Zabbix database. Successful exploitation yields full control over the database contents and, given the CVSS scope change, can lead to high-impact effects on confidentiality, integrity, and availability of the monitoring platform.
The referenced Zabbix support advisory ZBX-24505 addresses the issue. The EPSS score has remained consistently high, reaching a peak of 0.9326.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-19716
Vulnerability details
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…
more
SQL injection.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Security testing and developer training directly verify and enforce proper input validation, reducing exploitability of injection and malformed-data weaknesses.
Security testing and evaluation at multiple SDLC stages directly detects missing or flawed input validation, with the required remediation process ensuring fixes are applied.
Directly implements checks on information inputs to reject invalid data before processing.
Spam protection mechanisms perform filtering and detection on inbound/outbound messages, directly compensating for missing or weak input validation of unsolicited content.