In the wazuh-slack active response script in Wazuh 4.2.x before 4.2.5, untrusted user agents are passed to a curl command line, potentially resulting in remote code execution.

Wazuh is a free and open source platform used for threat prevention, detection, and response. A wrong validation in the hostdeny script allows to write any string in the hosts.deny file, which can end in an arbitrary command execution on the target system. This vulnerability is part of the active response feature, which can automatically triggers actions in response to alerts. By default, active responses are limited to a set of pre defined executables. This is enforced by only allowing executables stored under /var/ossec/active-response/bin to be run as an active response. However, the /var/ossec/active-response/bin/hostdeny can be exploited. hostdeny is used to add IP address to the /etc/hosts.deny file to block incoming connections on a service level by using TCP wrappers. Attacker can inject arbitrary command into the /etc/hosts.deny file and execute arbitrary command by using the spawn directive. The active response can be triggered by writing events either to the local execd queue on server or to the ar queue which forwards the events to agents. So, it can leads to LPE on server as root and RCE on agent as root. This vulnerability is fixed in 4.7.2.