# CVE-2023-20519: Use after free in 3rd Gen AMD EPYC™ Processors

> A malicious hypervisor can exploit a use-after-free flaw in AMD EPYC processors to masquerade as a migration agent, compromising guest integrity.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Nov 2023
- **Updated:** 30 Aug 2024
- **Also known as:** GHSA-3pww-pqg2-m2hm

## What is CVE-2023-20519?

CVE-2023-20519 is a low-severity use after free vulnerability in 3rd Gen AMD EPYC™ Processors, published on 14 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Use-After-Free vulnerability in the management of an SNP guest context page may allow a malicious hypervisor to masquerade as the guest's migration agent resulting in a potential loss of guest integrity.

Weakness: CWE-416 (Use After Free)

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

It affects 2 products.


Products: Amd Genoapi Firmware, Amd Milanpi Firmware.

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

Apply the vendor's patch.

## Is CVE-2023-20519 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-20519 is a low-severity use after free vulnerability in 3rd Gen AMD EPYC™ Processors, published on 14 Nov 2023. 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-20519 in the wild and no public exploit code.

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

## Sources

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

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