CloudstackApplication · Apache
CVE-2024-29006
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 · uneditedBy default the CloudStack management server honours the x-forwarded-for HTTP header and logs it as the source IP of an API request. This could lead to authentication bypass and other operational problems should an attacker decide to spoof their IP address this way. Users are recommended to upgrade to CloudStack 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 management server by default trusts and logs the X-Forwarded-For HTTP header as the source IP for API requests without validation. This allows attackers to spoof their IP address by supplying a crafted X-Forwarded-For header, potentially bypassing IP-based authentication, rate limiting, and other security controls that rely on source IP verification.
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.11.0.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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify CloudStack installation and versionRun 'cloudstack-sysvm' or check the management server package version using your system's package manager (e.g., rpm -q cloudstack-management or dpkg -l cloudstack-management). Alternatively, check the UI footer or API response for the version number.Affected if The installed version is >= 4.11.0.0 and < 4.18.1.1, or exactly 4.19.0.0.
-
Determine if management server is exposed directlyReview your network architecture or firewall rules to determine if the CloudStack management server (port 8080 or 8443 by default) is directly accessible from untrusted networks, or if a reverse proxy/load balancer sits in front of it.Affected if The management server is directly accessible without an intervening proxy that can strip or validate X-Forwarded-For headers.
-
Check for reverse proxy or load balancer configurationInspect the configuration of any reverse proxy (e.g., Nginx, Apache HTTPd) or load balancer (e.g., HAProxy, AWS ALB) sitting in front of CloudStack. Look for settings related to X-Forwarded-For header handling, such as 'proxy_set_header X-Forwarded-For', 'RequestHeader set', or similar directives.Affected if No proxy exists, or the proxy is configured to pass X-Forwarded-For headers to CloudStack without validation or stripping.
-
Verify API access methodCheck how API requests reach the CloudStack management server by reviewing your API client configuration or network routing. Determine if requests originate from a trusted proxy or directly from clients.Affected if API clients can directly supply X-Forwarded-For headers in their requests to the management server.
You are affected if you are running a vulnerable CloudStack version (4.11.0.0 through 4.18.1.0 or 4.19.0.0) with the management server directly exposed or behind a proxy that does not strip or validate X-Forwarded-For headers.
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 CloudStack to version 4.18.1.1 or 4.19.0.1, which fixes the improper validation of the X-Forwarded-For header. Alternatively, implement network-level controls to strip or validate X-Forwarded-For headers at load balancers/proxies before they reach the management server.
CloudStack 4.18.1.1 or 4.19.0.1
- 1. Verify current CloudStack management server version using 'cloudmonkey' or management server logs
- 2. Perform a complete backup of the CloudStack database and configuration files
- 3. Download CloudStack version 4.18.1.1 or 4.19.0.1 from the official Apache CloudStack repository
- 4. Stop the CloudStack management server services
- 5. Upgrade the CloudStack packages following the official upgrade documentation for your specific version path
- 6. Run database migration scripts included in the upgrade
- 7. Restart the CloudStack management server services
- 8. Verify the management server is running and validate that X-Forwarded-For header is no longer trusted by default
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Cloudstack
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing8.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29006 — 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-29006 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