CVE-2024-29007
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 · uneditedThe CloudStack management server and secondary storage VM could be tricked into making requests to restricted or random resources by means of following 301 HTTP redirects presented by external servers when downloading templates or ISOs. Users are recommended 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 confidenceApache CloudStack's management server and secondary storage VM follow 301 HTTP redirects from external servers when downloading templates or ISOs, allowing attackers to redirect download requests to restricted or arbitrary resources by controlling the redirect response.
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>= 4.9.1.0, < 4.18.1.1= 4.19.0.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache CloudStack management server versionRun 'cloudstack-scripts --version' or check the RPM/Debian package version (e.g., 'rpm -q cloudstack-management'), or look in the UI under 'About CloudStack' in the administration sectionAffected if Installed version is >= 4.9.1.0 and < 4.18.1.1, or equals exactly 4.19.0.0
-
Confirm secondary storage is configured with external HTTP sourcesReview CloudStack secondary storage pool configuration: navigate to Infrastructure > Secondary Storage in the CloudStack UI, or inspect the 'secondary.storage.pool' configuration entries in the CloudStack database or configuration filesAffected if Secondary storage is configured to fetch templates/ISOs from external HTTP/HTTPS URLs rather than only from locally attached storage
-
Check if template or ISO download from URLs is enabledExamine the CloudStack global settings for 'secstorage.allowed.internal.sites' or similar URL download settings, and review whether templates/ISOs have been registered with HTTP/HTTPS URLs (check in Templates or ISOs section of the UI)Affected if External URL-based template/ISO registration is permitted and has been used in the environment
-
Verify redirect handling in download workflowsReview CloudStack logs for any redirect activity during template/ISO downloads, or test by registering a template from a controlled HTTP server that sends a 301 redirect to verify if redirects are followedAffected if The system follows HTTP 301 redirects when downloading templates or ISOs from external sources
You are affected if your CloudStack version falls within the vulnerable range AND you use external HTTP/HTTPS sources for template or ISO downloads that could be redirected by an attacker.
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.1.1
Upgrade to Apache CloudStack version 4.18.1.1 or 4.19.0.1 which adds proper validation of HTTP redirect targets.
4.18.1.1 or 4.19.0.1
- 1. Back up the CloudStack database and configuration files before starting the upgrade process
- 2. Stop the CloudStack management server service
- 3. Update the CloudStack packages to version 4.18.1.1 or 4.19.0.1 using the package manager (e.g., apt-get upgrade or yum update)
- 4. If required, run database migration scripts provided in the upgrade
- 5. Start the CloudStack management server service
- 6. Verify that the management server is running and accessible
- 7. Test template and ISO download functionality to confirm the SSRF fix is working
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.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 $5,536.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29007 — 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-29007 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