CVE-2024-42329

What it actually does

Null pointer dereference occurs in the webdriver when webdriver_session_query fails without initializing an error object, leaving wd->error as NULL and triggering a crash on subsequent access.

Why it matters to the business

Unexpected crashes can disrupt Zabbix monitoring and automation workflows, leading to temporary loss of visibility into infrastructure health and potential delays in incident response.

How an attack unfolds

An attacker supplies input or conditions that cause webdriver_session_query to fail without an error description; the code then attempts to read from the uninitialized NULL pointer in the Browser object's error handling path, resulting in a process crash.

How to fix it

Upgrade Zabbix to the fixed commit f383737f1083e25756c6afaaa8abff05ad11eb50 in the GIT repository to ensure proper error object initialization before any access.

How to confirm the fix worked

Confirm the patched commit is present in the source tree, then exercise known failure paths in webdriver_session_query to verify no NULL dereference occurs.

Typical attack path

1. Trigger a failure path in webdriver_session_query without providing an error object
2. Allow execution to reach the point where wd->error is dereferenced
3. Cause segmentation fault and service termination

How to detect it

Search Zabbix logs and system crash reports for segmentation faults or abnormal terminations involving webdriver or Browser object handling.

What your security team should do

• Apply the fix from commit f383737f1083e25756c6afaaa8abff05ad11eb50 without delay
• Monitor Zabbix process stability for browser-related components
• Review dependent automation scripts that invoke the Browser object for error resilience