dbcve.org
WazuhApplication

CVE-2024-47770

HIGH · 8.0 CVSS v3.1 Published 2025-02-03
Fix available
A fix is available. Upgrade to 4.9.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Wazuh dashboard contains an improper access control vulnerability that allows low-privilege or unauthenticated attackers to view the agent list, enabling privilege escalation. The vulnerability stems from insufficient authorization checks on the agent enumeration endpoint.

MitigationUpgrade Wazuh to version 4.9.1 or later. No workarounds are available; immediate patching is required given the CVSS 8 severity and potential for privilege escalation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WazuhApplication
Affected:< 4.9.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Wazuh dashboard version
    Locate the Wazuh dashboard version file or check via the web UI footer. Common paths include /usr/share/wazuh-dashboard/package.json or the About section in the dashboard. Alternatively, check the installed package: dpkg -l | grep wazuh-dashboard or rpm -qa | grep wazuh-dashboard
    Affected if The installed version is lower than 4.9.1 (e.g., 4.9.0, 4.8.x, 4.7.x, etc.)
  2. Identify Wazuh dashboard API endpoint configuration
    Examine the Wazuh dashboard configuration files (typically in /etc/wazuh-dashboard/ or /opt/wazuh-dashboard/config/) for API endpoint definitions. Look for the agents endpoint configuration (commonly /agents)
    Affected if The dashboard is configured to connect to a Wazuh manager API and the agent enumeration endpoint is exposed
  3. Test agent enumeration endpoint access
    Make an unauthenticated or low-privilege HTTP request to the agents API endpoint (e.g., GET /api/v1/agents) using curl or a similar tool. No authentication headers or invalid credentials should be used to simulate an unauthenticated or low-privilege attacker
    Affected if The request returns agent data (JSON containing agent IDs, names, or status) without requiring proper authentication or returns HTTP 200 instead of 401/403
  4. Review user role and permission configuration
    Check the Wazuh dashboard user roles in /etc/wazuh-dashboard/opensearch_dashboards.yml or the internal security index. Look for roles assigned to standard users and whether they have agent:read permission
    Affected if Standard or low-privilege users are assigned roles that incorrectly grant access to agent enumeration endpoints

A user is affected if the Wazuh dashboard version is below 4.9.1 AND the agent enumeration API endpoint returns agent data to unauthenticated or low-privilege users without proper authorization checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.9.1 or later
Fixed in 4.9.1
Interim mitigation

Upgrade Wazuh to version 4.9.1 or later. No workarounds are available; immediate patching is required given the CVSS 8 severity and potential for privilege escalation.

Recommended fix High confidence

4.9.1

  1. Back up current Wazuh configuration and data before starting the upgrade
  2. Stop all Wazuh services to ensure a clean upgrade process
  3. Upgrade Wazuh to version 4.9.1 using the official upgrade method for your deployment type
  4. After upgrade, verify that all services start successfully
  5. Confirm the vulnerability is remediated by verifying that unauthorized users can no longer view the agent list without proper privileges

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wazuh Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47770 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-47770 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data