dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-57378

HIGH · 7.3 CVSS v3.1 Published 2025-02-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 SIEM version 4.8.2 is affected by a broken access control vulnerability. This issue allows the unauthorized creation of internal users without assigning any existing user role, potentially leading to privilege escalation or unauthorized access to sensitive resources.

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 SIEM 4.8.2 contains a broken access control vulnerability in its user management functionality that allows unauthorized actors to create internal users without assigning any role. This bypasses the intended role-based access control (RBAC) mechanism, potentially granting access to sensitive security monitoring data and administrative functions.

MitigationApply vendor patches or updates to Wazuh SIEM that address the access control validation in user creation workflows. Implement strict role assignment requirements and audit user creation APIs.

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

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Identify Wazuh SIEM installed version
    Run the command: /var/ossec/bin/wazuh-control info (or check the Wazuh dashboard about section) to retrieve the installed version number.
    Affected if Version is 4.8.2 or falls within the affected release range prior to patch application.
  2. Verify API user creation endpoint accessibility
    Check if the Wazuh API endpoint /security/user (POST method) is exposed and accessible. Inspect API configuration files (typically in /var/ossec/api/configuration) for endpoint exposure and authentication requirements.
    Affected if The user creation API endpoint is accessible without proper authorization or role validation.
  3. Enumerate existing users without assigned roles
    Query the Wazuh API using GET /security/user to list all users and their role assignments. Examine the response for any users where the 'roles' field is empty, null, or missing.
    Affected if Any internal user account exists in the system without an assigned role.
  4. Review audit logs for unauthorized user creation
    Check Wazuh audit logs (typically in /var/ossec/logs/audit/audit.log) for user creation events. Look for POST requests to /security/user where the created user has no role assignment.
    Affected if Audit logs show user creation events with no role assignment, indicating the vulnerability may have been exploited.
  5. Confirm RBAC enforcement on user management
    Inspect the Wazuh internal security configuration (check /var/ossec/api/configuration/security.yaml or via API GET /security/config) to verify role-based access control is properly enforced for user creation operations.
    Affected if RBAC validation is disabled, misconfigured, or allows user creation without mandatory role assignment.

You are affected if running Wazuh SIEM 4.8.2 (or unpatched version) AND the user creation API is accessible AND any user exists without an assigned role, indicating the broken access control bypassed RBAC.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches or updates to Wazuh SIEM that address the access control validation in user creation workflows. Implement strict role assignment requirements and audit user creation APIs.

Recommended fix Moderate confidence

Wazuh 4.8.3 or later (verify exact version from official Wazuh security advisory)

  1. Check the official Wazuh security advisories or release notes for CVE-2024-57378 to identify the specific fixed version
  2. If a fixed version (e.g., 4.8.3 or higher) is available, plan the upgrade following Wazuh's standard upgrade documentation
  3. Before upgrading, backup the Wazuh configuration and any custom files
  4. Test the upgrade in a non-production environment first
  5. After upgrading, verify that the access control vulnerability is remediated by attempting to create a user without proper authorization (this should now be denied)
Caveat Review Wazuh release notes for any breaking changes between 4.8.2 and the target version before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-57378 — 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-57378 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