CVE-2024-42326

What it actually does

Use-after-free in es_browser_get_variant within browser.c leading to memory corruption.

Why it matters to the business

May allow remote attackers to crash the Zabbix server or execute arbitrary code, disrupting infrastructure monitoring and alerting.

How an attack unfolds

An attacker supplies input that causes the es_browser_get_variant function to reference memory after it has been freed, enabling memory manipulation that can lead to code execution.

How to fix it

Upgrade Zabbix GIT to commit d93ce022627d3f10608b774e322cde3c961453e3 or later.

How to confirm the fix worked

Confirm the running version contains commit d93ce022627d3f10608b774e322cde3c961453e3; recompile and test the browser module for absence of the use-after-free condition.

Typical attack path

1. Locate an exposed Zabbix instance
2. Trigger the browser component with crafted input
3. Induce use-after-free in es_browser_get_variant
4. Leverage resulting memory corruption for code execution or denial of service

How to detect it

Review Zabbix process logs and core dumps for browser.c crashes or heap errors; inspect network logs for unusual requests targeting browser endpoints.

What your security team should do

• Apply the referenced commit immediately
• Restrict network access to Zabbix web and API endpoints
• Enable memory safety tooling and crash logging on Zabbix servers