CloudstackApplication · Apache

CVE-2024-29007

HIGH · 7.3 CVSS v3.1 Published 2024-04-04
Fix available
A fix is available. Upgrade to 4.18.1.1 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges 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
The 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 confidence

Apache 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.

MitigationUpgrade to Apache CloudStack version 4.18.1.1 or 4.19.0.1 which adds proper validation of HTTP redirect targets.

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.9.1.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
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 checks

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

  1. Identify Apache CloudStack management server version
    Run '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 section
    Affected if Installed version is >= 4.9.1.0 and < 4.18.1.1, or equals exactly 4.19.0.0
  2. Confirm secondary storage is configured with external HTTP sources
    Review 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 files
    Affected if Secondary storage is configured to fetch templates/ISOs from external HTTP/HTTPS URLs rather than only from locally attached storage
  3. Check if template or ISO download from URLs is enabled
    Examine 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
  4. Verify redirect handling in download workflows
    Review 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 followed
    Affected 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.

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 Apache CloudStack version 4.18.1.1 or 4.19.0.1 which adds proper validation of HTTP redirect targets.

Recommended fix High confidence

4.18.1.1 or 4.19.0.1

  1. 1. Back up the CloudStack database and configuration files before starting the upgrade process
  2. 2. Stop the CloudStack management server service
  3. 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. 4. If required, run database migration scripts provided in the upgrade
  5. 5. Start the CloudStack management server service
  6. 6. Verify that the management server is running and accessible
  7. 7. Test template and ISO download functionality to confirm the SSRF fix is working
Caveat Review release notes for any configuration changes or deprecations between your current version and the target version before upgrading

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

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

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 locally
dbcve dependency scanner

Check 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-29007 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