dbcve.org
CloudstackApplication · Apache

CVE-2025-47849

HIGH · 8.8 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 4.19.3.0 / 4.20.1.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
A privilege escalation vulnerability exists in Apache CloudStack versions 4.10.0.0 through 4.20.0.0 where a malicious Domain Admin user in the ROOT domain can get the API key and secret key of user-accounts of Admin role type in the same domain. This operation is not appropriately restricted and allows the attacker to assume control over higher-privileged user-accounts. A malicious Domain Admin attacker can impersonate an Admin user-account and gain access to sensitive APIs and resources that could result in the compromise of resource integrity and confidentiality, data loss, denial of service, and availability of infrastructure managed by CloudStack. Users are recommended to upgrade to Apache CloudStack 4.19.3.0 or 4.20.1.0, which fixes the issue with the following: * Strict validation on Role Type hierarchy: the caller's role must be equal to or higher than the target user's role.  * API privilege comparison: the caller must possess all privileges of the user they are operating on.  * Two new domain-level settings (restricted to the default admin):   - role.types.allowed.for.operations.on.accounts.of.same.role.type: Defines which role types are allowed to act on users of the same role type. Default: "Admin, DomainAdmin, ResourceAdmin".   - allow.operations.on.users.in.same.account: Allows/disallows user operations within the same account. Default: true.

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 confidence

Apache CloudStack versions 4.10.0.0-4.20.0.0 contain a privilege escalation flaw where a Domain Admin in the ROOT domain can retrieve API/secret keys of Admin role users in the same domain, allowing impersonation of higher-privileged accounts. The vulnerability stems from insufficient enforcement of role hierarchy and privilege boundaries when accessing user credentials.

MitigationUpgrade to Apache CloudStack 4.19.3.0 or 4.20.1.0 which implements strict role type hierarchy validation, API privilege comparison, and new domain-level security settings to restrict unauthorized access to higher-privileged user credentials.

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
Affected:>= 4.10.0.0, < 4.19.3.0>= 4.20.0.0, < 4.20.1.0

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed CloudStack version
    Query the CloudStack API endpoint 'listInfrastructure' or check the management server's /usr/share/cloudstack-common/scripts/util/cloudstack-usage-version.sh, or inspect the RPM/DEB package version with 'rpm -q cloudstack-management' or 'dpkg -l cloudstack-management'
    Affected if The installed version falls within >= 4.10.0.0 and < 4.19.3.0, or >= 4.20.0.0 and < 4.20.1.0
  2. Verify the presence of Domain Admin users in the ROOT domain
    Use the CloudStack API 'listUsers' command with domainid=ROOT (or the UUID of the ROOT domain) to enumerate users assigned to the ROOT domain. Alternatively, query the user table in the CloudStack database for users where domain_id corresponds to the ROOT domain and account_type indicates DomainAdmin (2)
    Affected if Any user with Domain Admin role exists within the ROOT domain
  3. Identify Admin role users who could be targeted
    Query the CloudStack API 'listUsers' or 'listAccounts' to identify users with role type 'Admin'. Check the database user table where account_type = 1 (Admin)
    Affected if Admin role users exist in the same domain as Domain Admin users (particularly ROOT domain)
  4. Confirm API key and secret key access is possible
    Attempt to retrieve user API keys via the 'getUserKeys' API call using credentials of a Domain Admin account in ROOT domain, or query the user table in the CloudStack database (user_api_key and user_secret_key columns) for Admin users
    Affected if Domain Admin credentials can successfully retrieve or view API/secret keys of Admin role users in the same domain

A system is affected if it runs a vulnerable CloudStack version (4.10.0.0-4.19.3.0 or 4.20.0.0-4.20.1.0) and contains Domain Admin users in the ROOT domain who can access API/secret keys of Admin role users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.19.3.0 / 4.20.1.0 or later
Fixed in 4.19.3.04.20.1.0
Interim mitigation

Upgrade to Apache CloudStack 4.19.3.0 or 4.20.1.0 which implements strict role type hierarchy validation, API privilege comparison, and new domain-level security settings to restrict unauthorized access to higher-privileged user credentials.

Recommended fix High confidence

Apache CloudStack 4.19.3.0 or 4.20.1.0

  1. 1. Perform a complete backup of the CloudStack database and configuration files before proceeding with the upgrade.
  2. 2. Stop all CloudStack services (management server, agents) following the standard shutdown procedure.
  3. 3. Update the package repository to point to the new CloudStack version.
  4. 4. Upgrade the CloudStack management server by installing the 4.19.3.0 (or 4.20.1.0) packages using the system package manager (e.g., apt-get or yum).
  5. 5. Run the CloudStack database upgrade scripts (cloudstack-upgrade -u or as documented in the upgrade guide).
  6. 6. Upgrade the CloudStack agents on all hypervisor hosts to match the new version.
  7. 7. Restart all CloudStack services in the correct order (management server first, then agents).
  8. 8. Verify the new domain-level settings are present: role.types.allowed.for.operations.on.accounts.of.same.role.type and allow.operations.on.users.in.same.account.
Caveat Review the official Apache CloudStack upgrade guide for version-specific migration steps and potential breaking changes between your current version and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cloudstack Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47849 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-47849 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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