Wazuh
Wazuh: Arbitrary File Deletion via Cluster Protocol – Incomplete Path Validation in end_receiving_file()
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 4.0.0, < 4.14.6
- >= 5.0.0-beta1, < 5.0.0-beta2
Fixed in 4.14.6, 5.0.0-beta2
Mitigation
Upgrade wazuh to 4.14.6 or 5.0.0-beta2 or later.
References
- Vendor advisory github.com/wazuh/wazuh/security/advisories/GHS…
- Patch github.com/wazuh/wazuh/pull/36060
- Patch github.com/wazuh/wazuh/commit/90d43547d166cdbe…
2 more
- Release notes github.com/wazuh/wazuh/releases/tag/v4.14.6
- Release notes github.com/wazuh/wazuh/releases/tag/v5.0.0-bet…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.