# CVE-2022-34147: Privilege escalation in Intel(R) NUC 9 Extreme Laptop Kits, Intel(R) NUC Performance Kits, Intel(R) NUC Performance Mini PC, Intel(R) NUC 8 Compute Element, Intel(R) NUC Pro Kit, Intel(R) NUC Pro Board, and Intel(R) NUC Compute Element

> A privileged local user can escalate privileges due to improper input validation in Intel NUC BIOS 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-q9qh-8m93-hm9h

## What is CVE-2022-34147?

CVE-2022-34147 is a high-severity vulnerability in Intel(R) NUC 9 Extreme Laptop Kits, Intel(R) NUC Performance Kits, Intel(R) NUC Performance Mini PC, Intel(R) NUC 8 Compute Element, Intel(R) NUC Pro Kit, Intel(R) NUC Pro Board, and Intel(R) NUC 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 BIOS firmware for some Intel(R) NUC 9 Extreme Laptop Kits, Intel(R) NUC Performance Kits, Intel(R) NUC Performance Mini PC, Intel(R) NUC 8 Compute Element, Intel(R) NUC Pro Kit, Intel(R) NUC Pro Board, and Intel(R) NUC Compute Element 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-34147?

It affects 41 products.


Products: Intel Cm8ccb4r Firmware, Intel Cm8i3cb4n Firmware, Intel Cm8i5cb8n Firmware, Intel Cm8i7cb8n Firmware, Intel Cm8pcb4r Firmware, Intel Lapqc71a Firmware, Intel Lapqc71b Firmware, Intel Lapqc71c Firmware, Intel Lapqc71d Firmware, Intel Nuc10i3fnh Firmware, Intel Nuc10i3fnhf Firmware, Intel Nuc10i3fnhfa Firmware, Intel Nuc10i3fnhja Firmware, Intel Nuc10i3fnhn Firmware, Intel Nuc10i3fnk Firmware, Intel Nuc10i3fnkn Firmware, Intel Nuc10i5fnh Firmware, Intel Nuc10i5fnhca Firmware, Intel Nuc10i5fnhf Firmware, Intel Nuc10i5fnhj Firmware and 21 more.

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

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

## Is CVE-2022-34147 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-34147 is a high-severity vulnerability in Intel(R) NUC 9 Extreme Laptop Kits, Intel(R) NUC Performance Kits, Intel(R) NUC Performance Mini PC, Intel(R) NUC 8 Compute Element, Intel(R) NUC Pro Kit, Intel(R) NUC Pro Board, and Intel(R) NUC 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-34147 in the wild and no public exploit code.

Affected product: Intel(R) NUC 9 Extreme Laptop Kits, Intel(R) NUC Performance Kits, Intel(R) NUC Performance Mini PC, Intel(R) NUC 8 Compute Element, Intel(R) NUC Pro Kit, Intel(R) NUC Pro Board, and Intel(R) NUC 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-34147/ (Markdown: https://insights.sbomify.com/CVE-2022-34147/index.md)
```

## Sources

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

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