CVE-2024-38346

Apache Cloudstack remote code execution

9.8 CRITICALEPSS 3.30%

Published5 Jul 2024

Description

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

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Apache Cloudstack≥ 4.0.0 < 4.18.2.1 · ≥ 4.19.0.0 < 4.19.0.2

Remediation

Fixed in

Apache Cloudstack≥ 4.18.2.1

Frequently asked

Is CVE-2024-38346 being actively exploited?

CVE-2024-38346 is not in the CISA KEV catalog. Its EPSS exploit probability is 3.30%.

How severe is CVE-2024-38346?

CVE-2024-38346 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 3.30% probability of exploitation.

Which products are affected by CVE-2024-38346?

Affected products include Apache Cloudstack.

How do I fix CVE-2024-38346?

Upgrade affected software to a fixed version, for example Apache Cloudstack 4.18.2.1 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-38346 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.