# CVE-2022-28699: Privilege escalation in Intel(R) NUC BIOS firmware

> 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-mpr4-2f6v-jf3q

## What is CVE-2022-28699?

CVE-2022-28699 is a high-severity vulnerability in Intel(R) NUC BIOS firmware, 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 for some Intel(R) NUC BIOS firmware 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-28699?

It affects 19 products.


Products: Intel Nuc7cjyh Firmware, Intel Nuc7cjyhn Firmware, Intel Nuc7cjysal Firmware, Intel Nuc7cjysamn Firmware, Intel Nuc7pjyh Firmware, Intel Nuc7pjyhn Firmware, Intel Nuc8cchb Firmware, Intel Nuc8cchbn Firmware, Intel Nuc8cchkr Firmware, Intel Nuc8cchkrn Firmware, Intel Nuc8i3cysn Firmware, Intel Nuc8i5inh Firmware, Intel Nuc8i7hnk Firmware, Intel Nuc8i7hnkqc Firmware, Intel Nuc8i7hvk Firmware, Intel Nuc8i7hvkva Firmware, Intel Nuc8i7hvkvaw Firmware, Intel Nuc8i7inh Firmware, Intel Stk2mv64cc Firmware.

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

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

## Is CVE-2022-28699 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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