# CVE-2023-42455: Wazuh vulnerable to user privilege escalation


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Oct 2023
- **Updated:** 19 Sep 2024

## What is CVE-2023-42455?

CVE-2023-42455 is a high-severity vulnerability in wazuh-kibana-app, published on 9 Oct 2023. 

### Official description

Wazuh is a security detection, visibility, and compliance open source project. In versions 4.4.0 and 4.4.1, it is possible to get the Wazuh API administrator key used by the Dashboard using the browser development tools. This allows a logged user to the dashboard to become administrator of the API, even if their dashboard role is not. Version 4.4.2 contains a fix. There are no known workarounds.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2023-42455?

It affects 2 products.


Products: Wazuh Wazuh-Dashboard, Wazuh Wazuh-Kibana-App.

## How do I fix CVE-2023-42455?

No fix has been published for CVE-2023-42455 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-42455 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-42455 and fix it if it is affected.

What it is: CVE-2023-42455 is a high-severity vulnerability in wazuh-kibana-app, published on 9 Oct 2023. 
Exploitation: There is no known exploitation of CVE-2023-42455 in the wild and no public exploit code.

Affected product: wazuh-kibana-app. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2023-42455/ (Markdown: https://insights.sbomify.com/CVE-2023-42455/index.md)
```

## Sources

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

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