# CVE-2023-34048: VMware vCenter Server Out-of-Bounds Write

> A remote attacker can trigger an out-of-bounds write in vCenter Server's DCERPC implementation to achieve remote code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 22 Jan 2024 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Oct 2023
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-87j2-5g9j-7jmv

## What is CVE-2023-34048?

CVE-2023-34048 is a critical memory corruption vulnerability in Vmware Vcenter Server, published on 25 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

vCenter Server contains an out-of-bounds write vulnerability in the implementation of the DCERPC protocol. A malicious actor with network access to vCenter Server may trigger an out-of-bounds write potentially leading to remote code execution.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2023-34048?

It affects 1 product.


Products: Vmware Vcenter Server.

## How do I fix CVE-2023-34048?

No fix has been published for CVE-2023-34048 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 12 Feb 2024.

## Is CVE-2023-34048 being exploited?

Yes. Attackers have exploited CVE-2023-34048 in the wild since at least 22 Jan 2024.

Public exploit code:

- VMware vCenter Server - Out-of-Bounds Write (nuclei): http/cves/2023/CVE-2023-34048.yaml

## Other vulnerabilities in Vmware Vcenter Server

- [CVE-2026-59310](https://insights.sbomify.com/CVE-2026-59310/): Broadcom VMware vCenter Path Traversal (critical 9.8, exploited in the wild)
- [CVE-2020-3952](https://insights.sbomify.com/CVE-2020-3952/): VMware vCenter Server Information Disclosure (critical 9.8, exploited in the wild)
- [CVE-2021-22017](https://insights.sbomify.com/CVE-2021-22017/): VMware vCenter Server Improper Access Control (medium 5.3, exploited in the wild)
- [CVE-2015-2342](https://insights.sbomify.com/CVE-2015-2342/): Code injection in n/a (critical 10.0)
- [CVE-2026-59309](https://insights.sbomify.com/CVE-2026-59309/): vCenter authentication-bypass vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-34048 and fix it if it is affected.

What it is: CVE-2023-34048 is a critical memory corruption vulnerability in Vmware Vcenter Server, published on 25 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2023-34048 in the wild since at least 22 Jan 2024.

Affected product: Vmware Vcenter Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-34048/ (Markdown: https://insights.sbomify.com/CVE-2023-34048/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-34048
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-34048
- OSV: https://osv.dev/vulnerability/CVE-2023-34048

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-34048/
Summaries are generated and may contain mistakes; the official description above is the record.
