# CVE-2024-47770: Ability to view Agent list with no privilege access in wazuh-dashboard

> Attackers can view the agent list without proper privileges, leading to unauthorized data access and potential privilege escalation in Wazuh dashboard.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Feb 2025
- **Updated:** 4 Feb 2025
- **Also known as:** GHSA-648q-8m78-5cwv, GO-2025-3445

## What is CVE-2024-47770?

CVE-2024-47770 is a medium-severity missing authorization vulnerability in Wazuh Wazuh, published on 3 Feb 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### 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. This vulnerability occurs when the system has weak privilege access, that allows an attacker to do privilege escalation. In this case the attacker is able to view agent list on Wazuh dashboard with no privilege access. This issue has been addressed in release version 4.9.1 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-269 (Improper Privilege Management)

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

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 | All versions | 4.9.1+incompatible |

Products: Wazuh Wazuh.

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

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

## Is CVE-2024-47770 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47770 exists.

## 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-47770 and fix it if it is affected.

What it is: CVE-2024-47770 is a medium-severity missing authorization vulnerability in Wazuh Wazuh, published on 3 Feb 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47770 exists.

Affected packages and fixed versions:
- github.com/wazuh/wazuh (Go): affected all versions; fixed in 4.9.1+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-47770/ (Markdown: https://insights.sbomify.com/CVE-2024-47770/index.md)
```

## Sources

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

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