CyberRota Analysis
AI-GeneratedWazuh versions 4.0.0 to 4.14.6 and 5.0.0-beta2 are vulnerable to a file deletion flaw that allows an authenticated cluster node to delete critical files outside the designated WAZUH_PATH. This vulnerability can lead to significant disruptions, including disabling the Wazuh manager, invalidating API tokens, and compromising cluster and API connectivity. Organizations using affected versions should prioritize upgrading to versions 4.14.6 or 5.0.0-beta2 to mitigate these risks.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.0.0 until 4.14.6 and 5.0.0-beta2, WazuhCommon.end_receiving_file() in framework/wazuh/core/cluster/common.py allows a cluster-authenticated node to delete files outside WAZUH_PATH. A syn_i_w_m_e request with an unknown task_id reaches the cleanup branch, where an attacker-controlled filename is passed to os.path.join without canonicalization or confinement. Absolute paths and traversal sequences can therefore target files such as ossec.conf, jwt_secret.json, TLS certificates, and ruleset files that are accessible to the Wazuh manager process. Deletion can disable the manager, invalidate API tokens, or disrupt cluster and API connectivity. This issue is fixed in versions 4.14.6 and 5.0.0-beta2.