CloudstackApplication · Apache
CVE-2024-45219
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 · uneditedAccount users in Apache CloudStack by default are allowed to upload and register templates for deploying instances and volumes for attaching them as data disks to their existing instances. Due to missing validation checks for KVM-compatible templates or volumes in CloudStack 4.0.0 through 4.18.2.3 and 4.19.0.0 through 4.19.1.1, an attacker that can upload or register templates and volumes, can use them to deploy malicious instances or attach uploaded volumes to their existing instances on KVM-based environments and exploit this to gain access to the host filesystems that could result in the compromise of resource integrity and confidentiality, data loss, denial of service, and availability of KVM-based infrastructure managed by CloudStack. Users are recommended to upgrade to Apache CloudStack 4.18.2.4 or 4.19.1.2, or later, which addresses this issue. Additionally, all user-uploaded or registered KVM-compatible templates and volumes can be scanned and checked that they are flat files that should not be using any additional or unnecessary features. For example, operators can run this on their secondary storage(s) and inspect output. An empty output for the disk being validated means it has no references to the host filesystems; on the other hand, if the output for the disk being validated is not empty, it might indicate a compromised disk. for file in $(find /path/to/storage/ -type f -regex [a-f0-9\-]*.*); do echo "Retrieving file [$file] info. If the output is not empty, that might indicate a compromised disk; check it carefully."; qemu-img info -U $file | grep file: ; printf "\n\n"; done The command can also be run for the file-based primary storages; however, bear in mind that (i) volumes created from templates will have references for the templates at first and (ii) volumes can be consolidated while migrating, losing their references to the templates. Therefore, the command execution for the primary storages can show both false positives and false negatives. For checking the whole template/volume features of each disk, operators can run the following command: for file in $(find /path/to/storage/ -type f -regex [a-f0-9\-]*.*); do echo "Retrieving file [$file] info."; qemu-img info -U $file; printf "\n\n"; done
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 confidenceMissing validation checks in Apache CloudStack allow account users to upload or register malicious KVM-compatible templates and volumes that contain filesystem path references. When deployed or attached in KVM-based environments, these templates/volumes enable attackers to escape instance isolation and access the host filesystem, compromising the hypervisor and underlying 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.0.0, < 4.18.2.4>= 4.19.0.0, < 4.19.1.2CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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.
-
Identify your CloudStack versionLocate the CloudStack management server installation and retrieve its version number (commonly via package manager, about page in UI, or admin API call)Affected if The installed version falls within >= 4.0.0 to < 4.18.2.4 OR >= 4.19.0.0 to < 4.19.1.2
-
Confirm KVM hypervisor is in useCheck the CloudStack infrastructure configuration to determine if KVM is enabled as a hypervisor type for any zone, cluster, or hostAffected if KVM-based zones, clusters, or hosts are present in the CloudStack environment
-
Verify user template/volume upload is permittedExamine CloudStack account permissions and service offerings to determine if non-admin users have the ability to upload or register custom templates or volumesAffected if Regular user accounts can upload, register, or add their own templates or volumes to the system
-
Inspect stored templates and volumes for path referencesOn secondary storage, use disk inspection tools (such as qemu-img or similar utilities capable of reading disk image metadata) to examine user-uploaded KVM-compatible templates and volumes for embedded host filesystem path referencesAffected if Any user-uploaded templates or volumes on secondary storage contain references to host filesystem paths outside the intended guest filesystem
You are affected if your CloudStack version is vulnerable AND KVM hypervisors are in use AND users can upload templates/volumes AND those uploaded assets contain host filesystem path references.
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.44.19.1.2
Upgrade to Apache CloudStack 4.18.2.4 or 4.19.1.2 or later to patch the validation vulnerability; additionally, scan all existing user-uploaded templates and volumes on secondary storage using qemu-img to identify and remove disks with host filesystem references.
4.18.2.4 or 4.19.1.2 (or later)
- Plan and schedule an upgrade to Apache CloudStack 4.18.2.4 or 4.19.1.2 (or later) based on your current major version branch
- Backup the CloudStack database and all critical configuration files before proceeding with the upgrade
- Stop CloudStack services (cloudstack-management, cloudstack-agents) on all nodes
- Follow the official Apache CloudStack upgrade documentation for your current version to upgrade to the target fixed release
- Start CloudStack services after the upgrade and verify all components are running correctly
- As an additional security measure, scan all user-uploaded KVM templates and volumes on secondary storage using: for file in $(find /path/to/storage/ -type f -regex '[a-f0-9\-]*.*'); do echo "Retrieving file [$file] info."; qemu-img info -U $file; printf "\n\n"; done
- Review any disks with non-empty 'file:' references in the output that might indicate compromised disks
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
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45219 — 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-45219 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