Vikman90

**Name of the Vulnerable Software and Affected Versions** Wazuh versions 4.0.0 through 4.14.5 **Description** An issue exists where authenticated cluster peers can delete arbitrary directory contents within the installation path writable by the wazuh user. This occurs because the system fails to validate the node name provided in the cluster hello payload. An attacker possessing a valid cluster Fernet key can provide a traversal-shaped node name and then disconnect, which triggers the master's peer cleanup routine to remove the specified directories. Path traversal is a technique used to access files or directories outside the intended folder by using special characters like dot-dot-slash. **Recommendations** Update Wazuh to version 4.14.6 or later.

**Name of the Vulnerable Software and Affected Versions** Wazuh wazuh-modulesd versions prior to 5.0.0-beta3 **Description** A null pointer dereference occurs in the `inventory sync` FlatBuffer DataValue handling. An enrolled agent can trigger a denial of service by sending a verifier-valid DataValue message that omits the optional `id` field. This causes the `wazuh-modulesd` process to crash when it attempts to dereference `data->id()->string view()` without performing null validation. **Recommendations** Update wazuh-modulesd to version 5.0.0-beta3 or later.

**Name of the Vulnerable Software and Affected Versions** Wazuh (affected versions not specified) **Description** The software contains an insecure transport issue due to the use of the `-k` or `--insecure` flag with `curl`, which disables SSL/TLS certificate validation. This allows attackers with network access to conduct man-in-the-middle attacks, potentially intercepting and modifying downloaded dependencies or code during the build process. Successful exploitation could lead to remote code execution and compromise the supply chain. The vulnerable component is the `curl` command used within the provisioning scripts and Dockerfiles. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Wazuh version 4.12.0 **Description** Wazuh version 4.12.0 has an issue where the `GITHUB TOKEN` can be extracted from uploaded artifacts in GitHub Actions workflows. This allows attackers to potentially perform unauthorized actions, such as pushing malicious commits or altering release tags, within a limited timeframe. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.