# CVE-2023-20512: Hardcoded credentials in AMD Radeon™ PRO W6000 Series Graphics Cards

> A hardcoded AES key in AMD Radeon firmware allows privileged attackers to leak internal debug information.

- **Severity:** Low 1.9 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/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:** No
- **Published:** 13 Aug 2024
- **Updated:** 30 Oct 2024
- **Also known as:** GHSA-ch37-5p65-5r4w

## What is CVE-2023-20512?

CVE-2023-20512 is a low-severity vulnerability in AMD Radeon™ PRO W6000 Series Graphics Cards, published on 13 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A hardcoded AES   key in PMFW may result in a privileged attacker gaining access to the key, potentially resulting in internal debug information leakage.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2023-20512 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-20512 is a low-severity vulnerability in AMD Radeon™ PRO W6000 Series Graphics Cards, published on 13 Aug 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-20512 in the wild and no public exploit code.

Affected product: AMD Radeon™ PRO W6000 Series Graphics Cards. 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-20512/ (Markdown: https://insights.sbomify.com/CVE-2023-20512/index.md)
```

## Sources

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

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