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

> Attackers can access protected memory regions on AMD EPYC processors due to insufficient access controls, potentially leading to data exposure or privilege escalation.

- **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-6582-243r-qxqj

## What is CVE-2018-8933?

CVE-2018-8933 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 EPYC Server processor chips have insufficient access control for protected memory regions, aka FALLOUT-1, FALLOUT-2, and FALLOUT-3.

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

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

It affects 1 product.


Products: Amd Epyc Server Firmware.

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

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

## Is CVE-2018-8933 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-8930](https://insights.sbomify.com/CVE-2018-8930/): Security feature bypass in n/a (critical 9.0)
- [CVE-2018-8936](https://insights.sbomify.com/CVE-2018-8936/): Privilege escalation in n/a (critical 9.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-8933 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-8933 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-8933/ (Markdown: https://insights.sbomify.com/CVE-2018-8933/index.md)
```

## Sources

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

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