CloudstackApplication · Apache
CVE-2024-38346
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 cluster service runs on unauthenticated port (default 9090) that can be misused to run arbitrary commands on targeted hypervisors and CloudStack management server hosts. Some of these commands were found to have command injection vulnerabilities that can result in arbitrary code execution via agents on the hosts that may run as a privileged user. An attacker that can reach the cluster service on the unauthenticated port (default 9090), can exploit this to perform remote code execution on CloudStack managed hosts and result in complete compromise of the confidentiality, integrity, and availability of CloudStack managed infrastructure. Users are recommended to restrict the network access to the cluster service port (default 9090) on a CloudStack management server host to only its peer CloudStack management server hosts. Users are recommended to upgrade to version 4.18.2.1, 4.19.0.2 or later, which addresses 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 confidenceCommand injection vulnerability in CloudStack's unauthenticated cluster service (port 9090) allows remote attackers to execute arbitrary code on hypervisors and management server hosts by injecting malicious commands through the agent service. The cluster service lacks authentication by default, enabling unauthenticated attackers who can reach port 9090 to compromise the entire CloudStack 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.1>= 4.19.0.0, < 4.19.0.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
- 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 versionRun 'cloudstack-sysvmtemplate' or check package manager for apache-cloudstack version, or query the CloudStack API at /api/api версияAffected if Installed version is 4.0.0 to <4.18.2.1 OR 4.19.0.0 to <4.19.0.2
-
Check if port 9090 is listeningRun 'netstat -tlnp | grep 9090' or 'ss -tlnp | grep 9090' on management server and hypervisor hostsAffected if Port 9090 is open and listening on any host
-
Verify cluster service statusCheck if the CloudStack agent service is running: 'systemctl status cloudstack-agent' or check for process 'Agent' on port 9090Affected if Agent process is running and bound to port 9090
-
Test network accessibility of port 9090From an external host, run 'nc -zv <target> 9090' or 'nmap -p 9090 <target>' to verify the port is reachable from untrusted networksAffected if Port 9090 is accessible from networks other than trusted management server peers
-
Confirm default unauthenticated accessReview CloudStack configuration files (agent.properties or similar) for 'cluster.service.auth' or similar settings, or attempt an unauthenticated request to the agent API on port 9090Affected if Cluster service has no authentication enabled (default configuration)
You are affected if your CloudStack version falls within the vulnerable range AND port 9090 is exposed and accessible to untrusted networks with default unauthenticated settings.
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.14.19.0.2
Restrict network access to port 9090 to only peer CloudStack management server hosts via firewall rules, and upgrade to version 4.18.2.1, 4.19.0.2 or later to address the command injection vulnerability.
4.18.2.1 or 4.19.0.2 (or later releases)
- Back up the CloudStack management server and database before starting the upgrade process
- Stop all CloudStack services (management server, agents)
- Upgrade CloudStack to version 4.18.2.1 (if currently on 4.0.0 - 4.18.x) or version 4.19.0.2 (if currently on 4.19.0.0 or 4.19.0.1)
- Run database upgrade scripts if provided with the release
- Start CloudStack services and verify they start without errors
- As an additional defense-in-depth measure, restrict network access to port 9090 on management server hosts to only trusted peer CloudStack management server IPs
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Cloudstack
Scoped from the published advisory
- Consultation6.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,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-38346 — 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-38346 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