# CVE-2024-42062: Apache CloudStack: User Key Exposure to Domain Admins

> Domain admins can view all API keys, including root admin keys, allowing privilege escalation and infrastructure compromise in Apache CloudStack.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Aug 2024
- **Updated:** 3 Sep 2024
- **Also known as:** GHSA-wrfv-q4v6-cw3x

## What is CVE-2024-42062?

CVE-2024-42062 is a high-severity missing authorization vulnerability in Apache Cloudstack, published on 7 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

CloudStack account-users by default use username and password based authentication for API and UI access. Account-users can generate and register randomised API and secret keys and use them for the purpose of API-based automation and integrations. Due to an access permission validation issue that affects Apache CloudStack versions 4.10.0 up to 4.19.1.0, domain admin accounts were found to be able to query all registered account-users API and secret keys in an environment, including that of a root admin. An attacker who has domain admin access can exploit this to gain root admin and other-account privileges and perform malicious operations that can result in compromise of resources integrity and confidentiality, data loss, denial of service and availability of CloudStack managed infrastructure.

Users are recommended to upgrade to Apache CloudStack 4.18.2.3 or 4.19.1.1, or later, which addresses this issue. Additionally, all account-user API and secret keys should be regenerated.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Apache Cloudstack.

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

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

## Is CVE-2024-42062 being exploited?

There is no known exploitation of CVE-2024-42062 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-38346](https://insights.sbomify.com/CVE-2024-38346/): Apache CloudStack: Unauthenticated cluster service port leads to remote execution (critical 9.8)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-42062 is a high-severity missing authorization vulnerability in Apache Cloudstack, published on 7 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-42062 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-42062/ (Markdown: https://insights.sbomify.com/CVE-2024-42062/index.md)
```

## Sources

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

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