# CVE-2023-45234: Buffer Overflow in EDK II Network Package

> Attackers can exploit a buffer overflow in EDK II's DHCPv6 processing to gain unauthorized access and compromise system integrity.

- **Severity:** High 8.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jan 2024
- **Updated:** 4 Nov 2025
- **Also known as:** AZL-38743, AZL-39118, AZL-39451, BELL-CVE-2023-45234, DEBIAN-CVE-2023-45234, GHSA-mrjv-p9q7-rxgr, RHSA-2024:1305, RHSA-2024:1722, UBUNTU-CVE-2023-45234

## What is CVE-2023-45234?

CVE-2023-45234 is a high-severity memory corruption vulnerability in TianoCore edk2, published on 16 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

EDK2's Network Package is susceptible to a buffer overflow vulnerability when processing DNS Servers option from a DHCPv6 Advertise message. This
 vulnerability can be exploited by an attacker to gain unauthorized 
access and potentially lead to a loss of Confidentiality, Integrity and/or Availability.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `edk2` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:20190829git37eef91017ad-9.el8_2.4 |
| `edk2-ovmf` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:20190829git37eef91017ad-9.el8_2.4 |
| `edk2` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:20200602gitca407c7246bf-4.el8_4.5 |
| `edk2-ovmf` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:20200602gitca407c7246bf-4.el8_4.5 |
| `edk2` | Red Hat:rhel_e4s:8.2::appstream | All versions | 0:20190829git37eef91017ad-9.el8_2.4 |
| `edk2-ovmf` | Red Hat:rhel_e4s:8.2::appstream | All versions | 0:20190829git37eef91017ad-9.el8_2.4 |
| `edk2` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:20200602gitca407c7246bf-4.el8_4.5 |
| `edk2-ovmf` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:20200602gitca407c7246bf-4.el8_4.5 |
| `edk2` | Red Hat:rhel_tus:8.2::appstream | All versions | 0:20190829git37eef91017ad-9.el8_2.4 |
| `edk2-ovmf` | Red Hat:rhel_tus:8.2::appstream | All versions | 0:20190829git37eef91017ad-9.el8_2.4 |
| `edk2` | Red Hat:rhel_tus:8.4::appstream | All versions | 0:20200602gitca407c7246bf-4.el8_4.5 |
| `edk2-ovmf` | Red Hat:rhel_tus:8.4::appstream | All versions | 0:20200602gitca407c7246bf-4.el8_4.5 |

Products: Tianocore Edk2.

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

Apply the vendor's patch.

## Is CVE-2023-45234 being exploited?

There is no known exploitation of CVE-2023-45234 in the wild and no public exploit code.

## Other vulnerabilities in TianoCore edk2

- [CVE-2023-45230](https://insights.sbomify.com/CVE-2023-45230/): Buffer Overflow in EDK II Network Package (high 8.3)
- [CVE-2023-45235](https://insights.sbomify.com/CVE-2023-45235/): Buffer Overflow in EDK II Network Package (high 8.3)
- [CVE-2021-28210](https://insights.sbomify.com/CVE-2021-28210/): Denial of service in EDK II (high 7.8)
- [CVE-2019-14584](https://insights.sbomify.com/CVE-2019-14584/): Null dereference in Tianocore EDK2 (high 7.8)
- [CVE-2017-5731](https://insights.sbomify.com/CVE-2017-5731/): Privilege escalation in Tianocore (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-45234 is a high-severity memory corruption vulnerability in TianoCore edk2, published on 16 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-45234 in the wild and no public exploit code.

Affected product: TianoCore edk2. 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-45234/ (Markdown: https://insights.sbomify.com/CVE-2023-45234/index.md)
```

## Sources

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

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