CyberRota Analysis
AI-GeneratedWazuh Manager versions 4.0.0 to 4.14.5 are vulnerable, allowing low-privilege read-only API users to access the cluster key through an insecure API endpoint. An attacker with network access to TCP port 1516 can exploit this vulnerability to impersonate a cluster worker, enabling them to create users, assign administrative roles, and modify configurations across the system. Organizations using affected versions of Wazuh should prioritize upgrading to version 4.14.5 to mitigate this high-severity risk.
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.5, Wazuh Manager allows a low-privilege read-only API user with manager:read permission to retrieve the cluster key from the element in ossec.conf through GET /manager/configuration?raw=true. An attacker with network access to TCP port 1516 can use the disclosed Fernet key to impersonate a cluster worker and submit distributed API requests containing attacker-controlled rbac_permissions with rbac_mode set to black. Because the master trusts the worker-supplied authorization context, the attacker can create users, assign administrator roles, access credentials and API tokens, modify configuration, and execute actions across agents. This issue is fixed in version 4.14.5.