CyberRota Analysis
AI-GeneratedWazuh versions 3.9.0 to 4.14.7 are vulnerable due to improper handling of payload buffer allocation in the cluster protocol, allowing unauthenticated network peers to exploit this by declaring excessively large payloads. This can lead to significant memory consumption, potentially causing the cluster process to terminate and disrupting synchronization and API functionality. Organizations using affected versions should prioritize patching to version 4.14.7 to mitigate this high-severity vulnerability.
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 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.