# CVE-2021-46766: Information disclosure in 4th Gen AMD EPYC™ Processors

> A privileged attacker can access secret keys from ASP SRAM due to improper data clearing in AMD EPYC bootloader firmware.

- **Severity:** Low 2.5 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Nov 2023
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-34xr-h92c-2m86

## What is CVE-2021-46766?

CVE-2021-46766 is a low-severity vulnerability in 4th 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

Improper clearing of sensitive data in the ASP Bootloader may expose secret keys to a privileged attacker accessing ASP SRAM, potentially leading to a loss of confidentiality.

Weakness: CWE-459 (Incomplete Cleanup)

## Which versions are affected by CVE-2021-46766?

It affects 28 products.


Products: Amd Epyc 9124 Firmware, Amd Epyc 9174f Firmware, Amd Epyc 9184x Firmware, Amd Epyc 9224 Firmware, Amd Epyc 9254 Firmware, Amd Epyc 9274f Firmware, Amd Epyc 9334 Firmware, Amd Epyc 9354 Firmware, Amd Epyc 9354p Firmware, Amd Epyc 9374f Firmware, Amd Epyc 9384x Firmware, Amd Epyc 9454 Firmware, Amd Epyc 9454p Firmware, Amd Epyc 9474f Firmware, Amd Epyc 9534 Firmware, Amd Epyc 9554 Firmware, Amd Epyc 9554p Firmware, Amd Epyc 9634 Firmware, Amd Epyc 9654 Firmware, Amd Epyc 9654p Firmware and 8 more.

## How do I fix CVE-2021-46766?

Apply the vendor's patch.

## Is CVE-2021-46766 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-46766 and fix it if it is affected.

What it is: CVE-2021-46766 is a low-severity vulnerability in 4th 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-2021-46766 in the wild and no public exploit code.

Affected product: 4th 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-2021-46766/ (Markdown: https://insights.sbomify.com/CVE-2021-46766/index.md)
```

## Sources

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

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