CVE-2024-38812
VMware vCenter Server Heap-Based Buffer Overflow Vulnerability
VMware vCenter Server
The vCenter Server contains a heap-overflow vulnerability in the implementation of the DCERPC protocol. A malicious actor with network access to vCenter Server may trigger this vulnerability by sending a specially crafted network packet potentially leading to remote code execution.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 20 November 2024. US federal agencies were required to remediate it by 11 December 2024.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 54.6%, which is higher than 99% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2024-38812 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2024-38812.
What does CVE-2024-38812 affect?
CVE-2024-38812 affects VMware vCenter Server. The vCenter Server contains a heap-overflow vulnerability in the implementation of the DCERPC protocol. A malicious actor with network access to vCenter Server may trigger this vulnerability by sending a specially crafted network packet potentially leading to remote code execution.
How severe is CVE-2024-38812?
CVE-2024-38812 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 54.6%, higher than 99% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 11 December 2024.
How should organisations respond to CVE-2024-38812?
Apply the vendor patch for VMware vCenter Server as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.