CVE-2024-39864
Apache Cloudstack remote code execution
- Published5 Jul 2024
Description
The CloudStack integration API service allows running its unauthenticated API server (usually on port 8096 when configured and enabled via integration.api.port global setting) for internal portal integrations and for testing purposes. By default, the integration API service port is disabled and is considered disabled when integration.api.port is set to 0 or negative. Due to an improper initialisation logic, the integration API service would listen on a random port when its port value is set to 0 (default value). An attacker that can access the CloudStack management network could scan and find the randomised integration API service port and exploit it to perform unauthorised administrative actions and 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 on the CloudStack management server hosts to only essential ports. 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
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
Frequently asked
Is CVE-2024-39864 being actively exploited?
CVE-2024-39864 is not in the CISA KEV catalog. Its EPSS exploit probability is 1.77%.
How severe is CVE-2024-39864?
CVE-2024-39864 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 1.77% probability of exploitation.
Which products are affected by CVE-2024-39864?
Affected products include Apache Cloudstack.
How do I fix CVE-2024-39864?
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-39864 against the real software inventory on every managed device, as each hourly inventory arrives. 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.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.