# CVE-2022-36339: Privilege escalation in Intel(R) NUC 8 Compute Element, Intel(R) NUC 11 Compute Element, Intel(R) NUC 12 Compute Element

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

- **Severity:** High 7.5 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/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:** 10 May 2023
- **Updated:** 27 Jan 2025
- **Also known as:** GHSA-mjmh-q76h-6245

## What is CVE-2022-36339?

CVE-2022-36339 is a high-severity vulnerability in Intel(R) NUC 8 Compute Element, Intel(R) NUC 11 Compute Element, Intel(R) NUC 12 Compute Element, published on 10 May 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 firmware for Intel(R) NUC 8 Compute Element, Intel(R) NUC 11 Compute Element, Intel(R) NUC 12 Compute Element may allow a privileged user to enable escalation of privilege via local access.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 13 products.


Products: Intel Cm11ebc4w Firmware, Intel Cm11ebi38w Firmware, Intel Cm11ebi58w Firmware, Intel Cm11ebi716w Firmware, Intel Cm8ccb4r Firmware, Intel Cm8i3cb4n Firmware, Intel Cm8i5cb8n Firmware, Intel Cm8i7cb8n Firmware, Intel Cm8pcb4r Firmware, Intel Elm12hbc Firmware, Intel Elm12hbi3 Firmware, Intel Elm12hbi5 Firmware, Intel Elm12hbi7 Firmware.

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

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

## Is CVE-2022-36339 being exploited?

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

## Other vulnerabilities in Intel(R) NUC 8 Compute Element, Intel(R) NUC 11 Compute Element, Intel(R) NUC 12 Compute Element

- [CVE-2022-37327](https://insights.sbomify.com/CVE-2022-37327/): Information disclosure in Intel(R) NUC, Intel(R) NUC Performance Kit, Intel(R) NUC Performance Mini PC, Intel(R) NUC 8 Compute Element, Intel(R) NUC Pro Kit, Intel(R) NUC Pro Board, Intel(R) NUC 11 Compute Element, Intel(R) NUC 12 Compute Element, Intel(R) NUC Extreme, Intel(R) NUC 12 Extreme Compute Element, Intel(R) NUC Laptop Kit, Intel(R) NUC Enthusiast, Intel(R) NUC Essential, Intel(R) NUC Laptop Kit, Intel(R) NUC Extreme Compute Element, Intel(R) NUC Boards, Intel(R) NUC Pro Compute Element, Intel(R) NUC Rugged (medium 6.1)
- [CVE-2022-31477](https://insights.sbomify.com/CVE-2022-31477/): Information disclosure in Intel(R) NUC BIOS firmware (medium 4.0)

## Fix prompt for AI coding agents

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

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

Affected product: Intel(R) NUC 8 Compute Element, Intel(R) NUC 11 Compute Element, Intel(R) NUC 12 Compute Element. 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-36339/ (Markdown: https://insights.sbomify.com/CVE-2022-36339/index.md)
```

## Sources

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

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