First published: Mon Feb 10 2025(Updated: )
Wazuh is a free and open source platform used for threat prevention, detection, and response. Starting in version 4.4.0 and prior to version 4.9.1, an unsafe deserialization vulnerability allows for remote code execution on Wazuh servers. DistributedAPI parameters are a serialized as JSON and deserialized using `as_wazuh_object` (in `framework/wazuh/core/cluster/common.py`). If an attacker manages to inject an unsanitized dictionary in DAPI request/response, they can forge an unhandled exception (`__unhandled_exc__`) to evaluate arbitrary python code. The vulnerability can be triggered by anybody with API access (compromised dashboard or Wazuh servers in the cluster) or, in certain configurations, even by a compromised agent. Version 4.9.1 contains a fix.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Wazuh | >=4.4.0<4.9.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-24016 has a severity rating that indicates a critical risk due to the potential for remote code execution.
To fix CVE-2025-24016, upgrade your Wazuh installation to version 4.9.1 or later.
CVE-2025-24016 affects Wazuh versions starting from 4.4.0 up to and including 4.9.0.
CVE-2025-24016 is categorized as an unsafe deserialization vulnerability.
Yes, CVE-2025-24016 can be exploited remotely, allowing attackers to execute arbitrary code on vulnerable servers.