# CVE-2018-8932: Missing authorization in n/a

> Attackers can bypass access controls on the AMD Secure Processor to execute arbitrary code or escalate privileges.

- **Severity:** Critical 9.0 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-p5rm-chg6-p3j7

## What is CVE-2018-8932?

CVE-2018-8932 is a critical missing authorization vulnerability in n/a, published on 22 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The AMD Ryzen and Ryzen Pro processor chips have insufficient access control for the Secure Processor, aka RYZENFALL-2, RYZENFALL-3, and RYZENFALL-4.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2018-8932?

It affects 2 products.


Products: Amd Ryzen Firmware, Amd Ryzen Pro Firmware.

## How do I fix CVE-2018-8932?

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

## Is CVE-2018-8932 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-8931](https://insights.sbomify.com/CVE-2018-8931/): Missing authorization in n/a (critical 9.0)
- [CVE-2018-8934](https://insights.sbomify.com/CVE-2018-8934/): Other in n/a (critical 9.0)
- [CVE-2018-8935](https://insights.sbomify.com/CVE-2018-8935/): Other in n/a (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-8932 and fix it if it is affected.

What it is: CVE-2018-8932 is a critical missing authorization vulnerability in n/a, published on 22 Mar 2018. 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-2018-8932 in the wild and no public exploit code.

Affected product: n/a. 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-2018-8932/ (Markdown: https://insights.sbomify.com/CVE-2018-8932/index.md)
```

## Sources

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

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