dbcve.org
CloudstackApplication · Apache

CVE-2024-29008

MEDIUM · 6.4 CVSS v3.1 Published 2024-04-04
Fix available
A fix is available. Upgrade to 4.18.1.1 or later.
See remediation →
70/100
Remediation priority · Elevated
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 problem has been identified in the CloudStack additional VM configuration (extraconfig) feature which can be misused by anyone who has privilege to deploy a VM instance or configure settings of an already deployed VM instance, to configure additional VM configuration even when the feature is not explicitly enabled by the administrator. In a KVM based CloudStack environment, an attacker can exploit this issue to attach host devices such as storage disks, and PCI and USB devices such as network adapters and GPUs, in a regular VM instance that can be further exploited to gain access to the underlying network and storage infrastructure resources, and access any VM instance disks on the local storage. Users are advised to upgrade to version 4.18.1.1 or 4.19.0.1, which fixes this issue.

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

A privilege bypass in Apache CloudStack allows users with VM deployment or configuration permissions to enable the extraconfig feature even when it is disabled by an administrator, enabling attachment of host devices (storage disks, PCI/USB devices, GPUs) to VMs in KVM environments.

MitigationUpgrade to CloudStack 4.18.1.1 or 4.19.0.1. Until patched, audit user permissions for VM deployment and monitor for unauthorized device attachment to VMs.

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.14.0.0, < 4.18.1.1= 4.19.0.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
Changed
Confidentiality
Low
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:L

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. Determine Apache CloudStack management server version
    Query the CloudStack API using `GET /client/api?command=listVersions` or check the management server JAR files in `/usr/share/cloudstack-management/` for the version. Also check the CloudStack about page in the UI.
    Affected if Installed version is 4.14.0.0 through 4.18.1.0 (exclusive), or exactly 4.19.0.0 (these are the vulnerable versions).
  2. Verify if the extraconfig feature is enabled
    Query the CloudStack global configuration via API: `GET /client/api?command=listConfigurations&name=extraconfig` or check the database table `cloud.configuration` where name='extraconfig'.
    Affected if The configuration value is set to 'true' - this means the vulnerable feature is active.
  3. Review VM instance device attachments in KVM environments
    Query the CloudStack API for VM instances with attached devices: `GET /client/api?command=listVolumes&type=datadisk` and check for any volume resources with 'DATADISK' type that were created unexpectedly. Also query `listRouters` and check for PCI device mappings in the database `cloud.vm_device` table where device_type contains 'PCI', 'USB', or 'GPU'.
    Affected if Unexpected data disks, PCI devices, USB devices, or GPU resources are attached to VMs without administrator authorization.
  4. Audit user account permissions for VM deployment and operations
    Query CloudStack user permissions via API: `GET /client/api?command=listUsers` and cross-reference with `listPermissions` or query the database `cloud.user_role` and `cloud.account` tables. Look for accounts with 'VM.DESTROY' or 'VM.DEPLOY' permissions granted to non-admin roles.
    Affected if Non-administrator users have been granted VM deployment, configuration, or device attachment permissions.

Your environment is affected if the CloudStack version is between 4.14.0.0 and 4.18.1.0 (exclusive) or exactly 4.19.0.0, and either the extraconfig feature is enabled or there is evidence of unauthorized device attachments to VMs.

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.18.1.1 or later
Fixed in 4.18.1.1
Interim mitigation

Upgrade to CloudStack 4.18.1.1 or 4.19.0.1. Until patched, audit user permissions for VM deployment and monitor for unauthorized device attachment to VMs.

Recommended fix High confidence

4.18.1.1 or 4.19.0.1

  1. 1. Backup the CloudStack database and configuration files before proceeding with the upgrade
  2. 2. Download the upgrade package for CloudStack version 4.18.1.1 or 4.19.0.1 from the official Apache CloudStack repository
  3. 3. Stop the CloudStack management server services
  4. 4. Upgrade the CloudStack management server using the standard upgrade process (e.g., running the systemvm template scripts or management server upgrade scripts)
  5. 5. Restart the CloudStack management server services
  6. 6. Verify that the extraconfig feature now properly enforces admin enablement before allowing additional VM configuration

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

Fix this in Cloudstack Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29008 — 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-2024-29008 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