Skip to content
Fencer Vulns
critical 9.8

CVE-2024-38812 kev in the critical feed json

Heap-overflow vulnerability

published 2024-09-17 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-37703

cvss
9.8
version 3.1, CNA
cisa kev
Exploited
added 2024-11-20
epss
54.6%
EPSS 54.6% chance of exploitation in 30 days, percentile 99%
public exploits
0
none known

Summary

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.

Patch / fix

cisa required action Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

  • n/a VMware vCenter Server 7.0 U3s, 8.0 U3b
  • broadcom vmware_vcenter_server 7.0u3s, 8.0u3b
  • broadcom vmware_cloud_foundation 5.0, 6.0

Timeline

  1. Published
  2. Added to CISA KEV
  3. CISA SSVC: exploitation active
  4. CISA patch deadline

Known exploited

Added
23 mo ago
Patch by
2024-12-11 (22 mo ago)
Ransomware
Not known
Required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Vendor, product
VMware, vCenter Server
CISA name
VMware vCenter Server Heap-Based Buffer Overflow Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
yes
Technical impact
total
Assessed
23 mo ago

Exploit prediction

54.57% chance of exploitation in the next 30 days, higher than 99% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • n/a VMware vCenter Server
  • n/a VMware Cloud Foundation
  • broadcom vmware_vcenter_server
  • broadcom vmware_cloud_foundation

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.