# CVE-2021-33086: Memory corruption in Intel(R) NUCs

> An authenticated local attacker can cause a denial of service via an out-of-bounds write in Intel NUC firmware.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** No
- **Published:** 17 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-82mx-gqwp-hp24

## What is CVE-2021-33086?

CVE-2021-33086 is a medium-severity memory corruption vulnerability in Intel(R) NUCs, published on 17 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Out-of-bounds write in firmware for some Intel(R) NUCs may allow an authenticated user to potentially enable denial of service via local access.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 103 products.


Products: Intel Nuc 10 Performance Kit Nuc10i3fnh Firmware, Intel Nuc 10 Performance Kit Nuc10i3fnhf Firmware, Intel Nuc 10 Performance Kit Nuc10i3fnhfa Firmware, Intel Nuc 10 Performance Kit Nuc10i3fnhja Firmware, Intel Nuc 10 Performance Kit Nuc10i3fnk Firmware, Intel Nuc 10 Performance Kit Nuc10i5fnh Firmware, Intel Nuc 10 Performance Kit Nuc10i5fnhca Firmware, Intel Nuc 10 Performance Kit Nuc10i5fnhf Firmware, Intel Nuc 10 Performance Kit Nuc10i5fnhj Firmware, Intel Nuc 10 Performance Kit Nuc10i5fnhja Firmware, Intel Nuc 10 Performance Kit Nuc10i5fnk Firmware, Intel Nuc 10 Performance Kit Nuc10i5fnkp Firmware, Intel Nuc 10 Performance Kit Nuc10i5fnkpa Firmware, Intel Nuc 10 Performance Kit Nuc10i7fnh Firmware, Intel Nuc 10 Performance Kit Nuc10i7fnhaa Firmware, Intel Nuc 10 Performance Kit Nuc10i7fnhc Firmware, Intel Nuc 10 Performance Kit Nuc10i7fnhja Firmware, Intel Nuc 10 Performance Kit Nuc10i7fnk Firmware, Intel Nuc 10 Performance Kit Nuc10i7fnkp Firmware, Intel Nuc 10 Performance Kit Nuc10i7fnkpa Firmware and 83 more.

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

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

## Is CVE-2021-33086 being exploited?

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

## Other vulnerabilities in Intel(R) NUCs

- [CVE-2022-37336](https://insights.sbomify.com/CVE-2022-37336/): Privilege escalation in Intel(R) NUC (high 7.9)
- [CVE-2022-36789](https://insights.sbomify.com/CVE-2022-36789/): Privilege escalation in Intel(R) NUC 10 Performance Kits and Intel(R) NUC 10 Performance Mini PCs (high 7.5)
- [CVE-2021-0054](https://insights.sbomify.com/CVE-2021-0054/): Privilege escalation in Intel(R) NUCs (medium 6.7)
- [CVE-2021-0067](https://insights.sbomify.com/CVE-2021-0067/): Privilege escalation in Intel(R) NUCs (medium 6.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-33086 is a medium-severity memory corruption vulnerability in Intel(R) NUCs, published on 17 Nov 2021. 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-33086 in the wild and no public exploit code.

Affected product: Intel(R) NUCs. 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-33086/ (Markdown: https://insights.sbomify.com/CVE-2021-33086/index.md)
```

## Sources

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

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