CVE-2024-38812
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.
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The attack is delivered via specially crafted network packets using the DCERPC protocol, which is not HTTP-based. Such packets do not resemble normal web traffic, but the protocol and packet contents are not HTTP requests, so a web application firewall cannot filter them.
Also consider: patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-38812 being exploited?
Yes. CVE-2024-38812 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-38812?
CVE-2024-38812 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-38812?
Yes. A fix has been recorded for CVE-2024-38812. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-38812 affect?
CVE-2024-38812 affects vmware:cloud_foundation, vmware:vcenter_server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected5.x
- affected4.x
- affected>= 8.0 and < 8.0 U3b
- affected>= 7.0 and < 7.0 U3s
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 20 Nov 2024 (SSVC 2.0.3).
timeline
- 17 Sept 2024Published
- 20 Nov 2024Added to CISA KEV (exploited in the wild) · 63 days (about 2 months) later
- 20 Nov 2024CISA SSVC assessment: exploitation active · 1 day later
- 11 Dec 2024CISA remediation due date (US federal agencies) · 20 days later
- 21 Oct 2025CVE record last updated · 315 days (about 11 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
- Linksupport.broadcom.com /web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/24
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-38812
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.