CVE-2024-42333

What it actually does

An out-of-bounds read in src/libs/zbxmedia/email.c allows a small amount of Zabbix Server process memory to be leaked via crafted email media operations.

Why it matters to the business

Limited sensitive data from server memory may be exposed to attackers, potentially assisting reconnaissance or further exploitation in environments using Zabbix for monitoring.

How an attack unfolds

An attacker supplies specially crafted input to email media handling that triggers the out-of-bounds read, causing the server to return a small portion of its memory contents in the response.

How to fix it

Upgrade Zabbix to a build containing commit f383737f1083e25756c6afaaa8abff05ad11eb50 or later; disable unused email media types until patched.

How to confirm the fix worked

Confirm the running binary or source matches a post-fix commit, re-test email media operations for absence of memory disclosure, and review changelog for the referenced commit.

Typical attack path

1. Locate a Zabbix Server instance exposing email media functionality
2. Craft and submit malicious input designed to trigger the out-of-bounds read in email.c
3. Capture and analyze the leaked memory fragment for useful data

How to detect it

Review Zabbix Server logs for email media errors or unexpected data patterns; inspect network responses from media handlers for anomalous content that may indicate memory leakage.

What your security team should do

• Prioritize upgrade of all Zabbix Server instances to the fixed commit
• Audit email media configurations and restrict to trusted destinations only
• Monitor EPSS and exploit maturity indicators for any future increase in risk