CVE-2023-32724

9.1 CRITICAL

📋 TL;DR

CVE-2023-32724 is a critical memory corruption vulnerability in Zabbix's Ducktape object that allows attackers to directly access and manipulate memory pointers. This can lead to arbitrary code execution, denial of service, or information disclosure. Organizations running vulnerable Zabbix versions are affected.

💻 Affected Systems

Products:
  • Zabbix
Versions: Zabbix 6.0.0 through 6.0.23, 6.2.0 through 6.2.11, 6.4.0 through 6.4.6, and 7.0.0alpha1
Operating Systems: All platforms running vulnerable Zabbix versions
Default Config Vulnerable: ⚠️ Yes
Notes: All Zabbix installations within affected version ranges are vulnerable regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote code execution with SYSTEM/root privileges leading to complete system compromise, data exfiltration, and lateral movement across the network.

🟠

Likely Case

Denial of service through application crashes or memory corruption, potentially leading to service disruption and data loss.

🟢

If Mitigated

Limited impact with proper network segmentation and access controls, potentially only causing application instability.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

The vulnerability requires specific memory manipulation techniques but is exploitable without authentication.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Zabbix 6.0.24, 6.2.12, 6.4.7, and 7.0.0alpha2

Vendor Advisory: https://support.zabbix.com/browse/ZBX-23391

Restart Required: Yes

Instructions:

1. Backup your Zabbix configuration and database. 2. Download the patched version from Zabbix official repository. 3. Stop Zabbix services. 4. Install the updated packages. 5. Restart Zabbix services. 6. Verify the upgrade was successful.

🔧 Temporary Workarounds

Network Access Restriction

linux

Restrict network access to Zabbix server and frontend to trusted IP addresses only

iptables -A INPUT -p tcp --dport 10051 -s trusted_ip -j ACCEPT
iptables -A INPUT -p tcp --dport 10051 -j DROP

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate Zabbix servers from critical systems
  • Deploy web application firewall (WAF) rules to detect and block exploitation attempts

🔍 How to Verify

Check if Vulnerable:

Check Zabbix version via web interface or command: zabbix_server --version

Check Version:

zabbix_server --version | grep -o '[0-9]\+\.[0-9]\+\.[0-9]\+'

Verify Fix Applied:

Verify version is 6.0.24, 6.2.12, 6.4.7, or 7.0.0alpha2 or higher

📡 Detection & Monitoring

Log Indicators:

  • Unexpected memory access errors in Zabbix logs
  • Application crashes or segmentation faults
  • Unusual process behavior or resource consumption

Network Indicators:

  • Unusual traffic patterns to Zabbix ports (10050, 10051, 80/443)
  • Multiple failed authentication attempts followed by exploitation attempts

SIEM Query:

source="zabbix.log" AND ("segmentation fault" OR "memory corruption" OR "access violation")

🔗 References

📤 Share & Export