# CVE-2022-37336: Privilege escalation in Intel(R) NUC

> A privileged local user can escalate privileges in Intel NUC BIOS firmware due to improper input validation.

- **Severity:** High 7.9 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:H`)
- **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:** 11 Aug 2023
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-rc2p-rrfm-r883

## What is CVE-2022-37336?

CVE-2022-37336 is a high-severity vulnerability in Intel(R) NUC, published on 11 Aug 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper input validation in BIOS firmware for some Intel(R) NUC may allow a privileged user to potentially enable escalation of privilege via local access.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2022-37336?

It affects 26 products.


Products: Intel Nuc 10 Performance Kit Nuc10i3fnh Firmware, Intel Nuc 10 Performance Kit Nuc10i3fnhf Firmware, Intel Nuc 10 Performance Kit Nuc10i3fnhn Firmware, Intel Nuc 10 Performance Kit Nuc10i3fnk Firmware, Intel Nuc 10 Performance Kit Nuc10i3fnkn Firmware, Intel Nuc 10 Performance Kit Nuc10i5fnh Firmware, Intel Nuc 10 Performance Kit Nuc10i5fnhf Firmware, Intel Nuc 10 Performance Kit Nuc10i5fnhj Firmware, Intel Nuc 10 Performance Kit Nuc10i5fnhn Firmware, Intel Nuc 10 Performance Kit Nuc10i5fnk Firmware, Intel Nuc 10 Performance Kit Nuc10i5fnkn Firmware, Intel Nuc 10 Performance Kit Nuc10i5fnkp Firmware, Intel Nuc 10 Performance Kit Nuc10i7fnh Firmware, Intel Nuc 10 Performance Kit Nuc10i7fnhc Firmware, Intel Nuc 10 Performance Kit Nuc10i7fnhn Firmware, Intel Nuc 10 Performance Kit Nuc10i7fnk Firmware, Intel Nuc 10 Performance Kit Nuc10i7fnkn Firmware, Intel Nuc 10 Performance Kit Nuc10i7fnkp Firmware, Intel Nuc 10 Performance Mini Pc Nuc10i3fnhfa Firmware, Intel Nuc 10 Performance Mini Pc Nuc10i3fnhja Firmware and 6 more.

## How do I fix CVE-2022-37336?

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

## Is CVE-2022-37336 being exploited?

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

## Other vulnerabilities in Intel(R) NUC

- [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)
- [CVE-2021-33086](https://insights.sbomify.com/CVE-2021-33086/): Memory corruption in Intel(R) NUCs (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-37336 and fix it if it is affected.

What it is: CVE-2022-37336 is a high-severity vulnerability in Intel(R) NUC, published on 11 Aug 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-2022-37336 in the wild and no public exploit code.

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

## Sources

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

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