Wazuh
Wazuh Manager cluster header parsing allows pre-authentication memory exhaustion
Wazuh is an open-source security platform providing unified XDR and SIEM protection for endpoints and cloud workloads. From 3.9.0 until 4.14.7, wazuh-clusterd in framework/wazuh/core/cluster/common.py allocates a payload buffer using the size declared in a 20-byte cluster protocol header before Fernet decryption validates the peer. An unauthenticated network peer can declare a payload of up to 256 MiB, stop sending after the header, and retain that allocation until the TCP connection closes. The cluster listener has no application-level per-source connection budget in affected versions, allowing concurrent sockets to multiply memory consumption and potentially terminate the cluster process, disrupt synchronization, and interrupt distributed API forwarding. This issue is fixed in version 4.14.7.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 3.9.0, < 4.14.7
Fixed in 4.14.7
Mitigation
Upgrade wazuh to 4.14.7 or later.
References
- Vendor advisory github.com/wazuh/wazuh/security/advisories/GHS…
- Patch github.com/wazuh/wazuh/pull/37280
- Patch github.com/wazuh/wazuh/commit/9a996bc23d28725f…
1 more
- Release notes github.com/wazuh/wazuh/releases/tag/v4.14.7
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.