# CVE-2024-38346: Apache CloudStack: Unauthenticated cluster service port leads to remote execution

> Unauthenticated access to the cluster service port allows command injection, leading to remote code execution and full compromise of managed hosts.

- **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:** 5 Jul 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-7g4v-8cvx-gp5q

## What is CVE-2024-38346?

CVE-2024-38346 is a critical command injection vulnerability in Apache Cloudstack, published on 5 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The CloudStack cluster service runs on unauthenticated port (default 9090) that can be misused to run arbitrary commands on targeted hypervisors and CloudStack management server hosts. Some of these commands were found to have command injection vulnerabilities that can result in arbitrary code execution via agents on the hosts that may run as a privileged user. An attacker that can reach the cluster service on the unauthenticated port (default 9090), can exploit this to perform remote code execution on CloudStack managed hosts and result in complete compromise of the confidentiality, integrity, and availability of CloudStack managed infrastructure.

Users are recommended to restrict the network access to the cluster service port (default 9090) on a CloudStack management server host to only its peer CloudStack management server hosts. Users are recommended to upgrade to version 4.18.2.1, 4.19.0.2 or later, which addresses this issue.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Apache Cloudstack.

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

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

## Is CVE-2024-38346 being exploited?

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

## Other vulnerabilities in Apache Cloudstack

- [CVE-2012-4501](https://insights.sbomify.com/CVE-2012-4501/): Missing authorization in n/a (critical 10.0)
- [CVE-2024-39864](https://insights.sbomify.com/CVE-2024-39864/): Apache CloudStack: Integration API service uses dynamic port when disabled (critical 9.8)
- [CVE-2024-29006](https://insights.sbomify.com/CVE-2024-29006/): Apache CloudStack: x-forwarded-for HTTP header parsed by default (critical 9.8)
- [CVE-2022-35741](https://insights.sbomify.com/CVE-2022-35741/): Apache CloudStack SAML Single Sign-On XXE (critical 9.8)
- [CVE-2019-17562](https://insights.sbomify.com/CVE-2019-17562/): Command injection in Apache CloudStack (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-38346 is a critical command injection vulnerability in Apache Cloudstack, published on 5 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-38346 in the wild and no public exploit code.

Affected product: Apache Cloudstack. 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-38346/ (Markdown: https://insights.sbomify.com/CVE-2024-38346/index.md)
```

## Sources

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

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