Wazuh
Wazuh: merged-file header path traversal in cluster sync allows arbitrary file write under WAZUH_PATH in Wazuh manager
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-beta3, cluster.unmerge_info() in framework/wazuh/core/cluster/cluster.py constructs paths from peer-controlled merge_type and name values in a merged synchronization archive. process_files_from_worker() in framework/wazuh/core/cluster/master.py does not adequately confine the resulting path to the declared cluster item directory. A cluster peer holding the shared Fernet key can use traversal in files_metadata.json or a merged-file header to write files such as /var/ossec/etc/ossec.conf. Replacing ossec.conf can configure root-executed commands and lead to code execution when Wazuh services reload. This issue is fixed in versions 4.14.6 and 5.0.0-beta3.
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-beta3
Fixed in 4.14.6, 5.0.0-beta3
Mitigation
Upgrade wazuh to 4.14.6 or 5.0.0-beta3 or later.
References
- Vendor advisory github.com/wazuh/wazuh/security/advisories/GHS…
- Patch github.com/wazuh/wazuh/pull/36204
- Patch github.com/wazuh/wazuh/commit/88fc89fdfb1bf37b…
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.