CloudstackApplication · Apache
CVE-2024-42062
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 · uneditedCloudStack 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.
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 · high confidenceThis is an authorization bypass vulnerability in Apache CloudStack where domain admin accounts could query all registered account-users API and secret keys in the environment, including those of root admins, due to improper access permission validation. This allows privilege escalation from domain admin to root admin level, enabling attackers to gain full control over CloudStack managed infrastructure.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
CloudstackApplication
>= 4.10.0.0, < 4.18.2.3>= 4.19.0.0, < 4.19.1.1CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Apache CloudStack versionCheck the CloudStack management server version by running: mysql -u cloud -p -e 'select name, value from cloud.configuration where name like "%version%";' or check the package version (rpm -q cloudstack-management or dpkg -l cloudstack-management)Affected if The installed version falls within the vulnerable ranges: >= 4.10.0.0 and < 4.18.2.3, OR >= 4.19.0.0 and < 4.19.1.1
-
Identify domain admin accounts in the environmentQuery the database: mysql -u cloud -p -e 'select id, username, account_id, type from cloud.user where type = 2;' (type 2 = domain admin)Affected if Domain admin accounts exist in the system, which are the potential attackers for this vulnerability
-
Review API access logs for unauthorized key queriesSearch CloudStack API logs (typically in /var/log/cloudstack/management/ or via database: select * from cloud_usage_event where api_name like '%UserKeys%' or api_name = 'queryUserKeys' or api_name = 'listUsers') for calls made by domain admin account_ids to retrieve other users API/secret keysAffected if Domain admin accounts have successfully queried API keys or secret keys for users outside their domain, including root admin accounts (account_type = 1)
-
Check for unexpected cross-domain user accessQuery the event log: mysql -u cloud -p -e 'select created, user_id, account_id, domain_id, type from cloud.event where type in ("USER_KEYS","QUERY_USER_KEYS") order by created desc;' to identify any user key queries that cross domain boundariesAffected if Domain admins (account.type = 2) have accessed user keys for users in different domains or with account_type = 1 (root admin)
A system is affected if it runs a vulnerable Apache CloudStack version (4.10.0.0 through 4.18.2.2 or 4.19.0.0 through 4.19.1.0) AND contains domain admin accounts that have accessed API/secret keys of users outside their domain, indicating the authorization bypass was exploited.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.18.2.34.19.1.1
Upgrade Apache CloudStack to version 4.18.2.3 or 4.19.1.1 or later to patch the access validation issue, and immediately regenerate all account-user API and secret keys to revoke any potentially compromised credentials.
4.18.2.3 or 4.19.1.1
- Upgrade Apache CloudStack to version 4.18.2.3 (if currently on 4.10.0.0-4.18.x) or 4.19.1.1 (if currently on 4.19.0.0-4.19.1.0), or a later stable release
- After upgrading, regenerate all account-user API keys and secret keys in the CloudStack environment to revoke any keys that may have been exfiltrated by a malicious domain admin
- Verify that only root admins can now access API/secret key information for users
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Cloudstack
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-42062 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-42062 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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