CVE-2024-36461

9.1 CRITICAL

📋 TL;DR

CVE-2024-36461 is a critical memory corruption vulnerability in Zabbix's JavaScript engine that allows authenticated users to directly modify memory pointers. This could lead to arbitrary code execution with the privileges of the Zabbix server process. All Zabbix installations with authenticated user access are affected.

💻 Affected Systems

Products:
  • Zabbix
Versions: Zabbix 7.0.0alpha1 through 7.0.0beta2
Operating Systems: All platforms running Zabbix
Default Config Vulnerable: ⚠️ Yes
Notes: Requires authenticated user access; default installations with web interface enabled are vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full system compromise through remote code execution, allowing attackers to execute arbitrary commands, steal data, or pivot to other systems.

🟠

Likely Case

Privilege escalation leading to unauthorized access to monitoring data, configuration manipulation, or denial of service.

🟢

If Mitigated

Limited impact if proper network segmentation and least privilege access controls are implemented, restricting exploit scope.

🌐 Internet-Facing: HIGH - Internet-facing Zabbix instances are directly accessible to attackers who can obtain or guess credentials.
🏢 Internal Only: HIGH - Internal attackers or compromised accounts can exploit this vulnerability to gain elevated privileges.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Exploitation requires authenticated access and knowledge of JavaScript engine internals; no public exploit code available at disclosure.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Zabbix 7.0.0beta3 and later

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

Restart Required: Yes

Instructions:

1. Backup Zabbix configuration and database. 2. Download Zabbix 7.0.0beta3 or later from official repository. 3. Stop Zabbix server and frontend services. 4. Install updated packages. 5. Restart Zabbix services. 6. Verify functionality.

🔧 Temporary Workarounds

Restrict User Access

all

Limit Zabbix web interface access to trusted users only and implement strong authentication controls.

Network Segmentation

all

Place Zabbix server behind firewall, restrict access to specific IP addresses, and disable internet-facing access.

🧯 If You Can't Patch

  • Implement strict access controls and multi-factor authentication for all Zabbix users.
  • Monitor Zabbix server logs for unusual JavaScript execution patterns or memory access attempts.

🔍 How to Verify

Check if Vulnerable:

Check Zabbix version via web interface (Administration → General → About) or command: zabbix_server --version

Check Version:

zabbix_server --version | grep '^zabbix_server'

Verify Fix Applied:

Confirm version is 7.0.0beta3 or higher and test JavaScript functionality in frontend.

📡 Detection & Monitoring

Log Indicators:

  • Unusual JavaScript execution errors in Zabbix server logs
  • Memory access violations in system logs

Network Indicators:

  • Unexpected outbound connections from Zabbix server
  • Anomalous HTTP requests to Zabbix web interface

SIEM Query:

source="zabbix_server.log" AND ("JavaScript error" OR "memory violation" OR "pointer access")

🔗 References

📤 Share & Export