# CVE-2022-23814: Other in 3rd Gen EPYC

> Attackers can compromise guest memory integrity in confidential compute environments by exploiting unvalidated BIOS command addresses in AMD EPYC processors.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jan 2023
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-hx9h-8469-xwvj

## What is CVE-2022-23814?

CVE-2022-23814 is a medium-severity vulnerability in AMD 3rd Gen EPYC, published on 10 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Failure to validate addresses provided by software to BIOS commands may result in a potential loss of integrity of guest memory in a confidential compute environment.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2022-23814?

It affects 1 product.


Products: Amd Milanpi-Sp3 Firmware.

## How do I fix CVE-2022-23814?

No fix has been published for CVE-2022-23814 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-23814 being exploited?

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

## Other vulnerabilities in AMD 3rd Gen EPYC

- [CVE-2022-23813](https://insights.sbomify.com/CVE-2022-23813/): Memory corruption in 2nd Gen EPYC (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-23814 and fix it if it is affected.

What it is: CVE-2022-23814 is a medium-severity vulnerability in AMD 3rd Gen EPYC, published on 10 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-23814 in the wild and no public exploit code.

Affected product: AMD 3rd Gen EPYC. 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-2022-23814/ (Markdown: https://insights.sbomify.com/CVE-2022-23814/index.md)
```

## Sources

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

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