# CVE-2024-35177: Improper Access Control in wazuh-agent

> A local attacker can escalate privileges to SYSTEM by placing malicious DLLs in the Wazuh agent installation directory when a non-default path is used.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Feb 2025
- **Updated:** 4 Feb 2025
- **Also known as:** GHSA-pmr2-2r83-h3cv, GO-2025-3444

## What is CVE-2024-35177?

CVE-2024-35177 is a high-severity vulnerability in Wazuh Wazuh, published on 3 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Wazuh is a free and open source platform used for threat prevention, detection, and response. It is capable of protecting workloads across on-premises, virtualized, containerized, and cloud-based environments. The wazuh-agent for Windows is vulnerable to a Local Privilege Escalation vulnerability due to improper ACL of the non-default installation directory. A local malicious user could potentially exploit this vulnerability by placing one of the many DLL that are loaded and not present on the system in the installation folder of the agent OR by replacing the service executable binary itself with a malicious one. The root cause is an improper ACL applied on the installation folder when a non-default installation path is specified (e.g,: C:\wazuh). Many DLLs are loaded from the installation folder and by creating a malicious DLLs that exports the functions of a legit one (and that is not found on the system where the agent is installed, such as rsync.dll) it is possible to escalate privileges from a low-privileged user and obtain code execution under the context of NT AUTHORITY\SYSTEM. This issue has been addressed in version 4.9.0 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2024-35177?

1 open source package ship an affected version, including github.com/wazuh/wazuh. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/wazuh/wazuh` | Go | From 3.0.0+incompatible | 4.9.0+incompatible |

Products: Wazuh Wazuh.

## How do I fix CVE-2024-35177?

Upgrade github.com/wazuh/wazuh to 4.9.0+incompatible or later.

## Is CVE-2024-35177 being exploited?

There is no known exploitation of CVE-2024-35177 in the wild and no public exploit code.

## Other vulnerabilities in Wazuh Wazuh

- [CVE-2025-24016](https://insights.sbomify.com/CVE-2025-24016/): Wazuh Server Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2024-32038](https://insights.sbomify.com/CVE-2024-32038/): Wazuh Analysis Engine Event Decoder Heap-based Buffer Overflow Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2021-44079](https://insights.sbomify.com/CVE-2021-44079/): Command injection in n/a (critical 9.8)
- [CVE-2024-1243](https://insights.sbomify.com/CVE-2024-1243/): Remote code execution and local privilege escalation in Wazuh Windows agent via NetNTLMv2 hash theft (critical 9.5)
- [CVE-2026-61800](https://insights.sbomify.com/CVE-2026-61800/): Wazuh cluster worker file sync allows arbitrary file write under /var/ossec (incomplete fix for CVE-2026-30893) (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-35177 and fix it if it is affected.

What it is: CVE-2024-35177 is a high-severity vulnerability in Wazuh Wazuh, published on 3 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-35177 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/wazuh/wazuh (Go): affected from 3.0.0+incompatible; fixed in 4.9.0+incompatible

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-35177/ (Markdown: https://insights.sbomify.com/CVE-2024-35177/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-35177
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-35177
- OSV: https://osv.dev/vulnerability/CVE-2024-35177

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-35177/
Summaries are generated and may contain mistakes; the official description above is the record.