# CVE-2024-13804: Auth bypass in HPE Insight Cluster Management Utility (CMU)

> Unauthenticated attackers can execute arbitrary code on HPE Insight Cluster Management Utility servers due to an authentication bypass vulnerability.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Mar 2025
- **Updated:** 31 Mar 2025
- **Also known as:** GHSA-j9fx-grxv-w3f9

## What is CVE-2024-13804?

CVE-2024-13804 is a critical authentication bypass vulnerability in Hewlett Packard Enterprise HPE Insight Cluster Management Utility (CMU), published on 30 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unauthenticated RCE in HPE Insight Cluster Management Utility

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2024-13804 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-13804 is a critical authentication bypass vulnerability in Hewlett Packard Enterprise HPE Insight Cluster Management Utility (CMU), published on 30 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-13804 exists.

Affected product: Hewlett Packard Enterprise HPE Insight Cluster Management Utility (CMU). 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-2024-13804/ (Markdown: https://insights.sbomify.com/CVE-2024-13804/index.md)
```

## Sources

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

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