# CVE-2022-38099: Privilege escalation in Intel(R) NUC 11 Compute Elements

> A privileged local user can escalate privileges due to improper input validation in Intel NUC 11 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:** 11 Nov 2022
- **Updated:** 5 Feb 2025
- **Also known as:** GHSA-m53v-6hgq-w7h2

## What is CVE-2022-38099?

CVE-2022-38099 is a high-severity vulnerability in Intel(R) NUC 11 Compute Elements, published on 11 Nov 2022. 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 11 Compute Elements before version EBTGL357.0065 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-38099?

It affects 8 products.


Products: Intel Nuc11dbbi7 Firmware, Intel Nuc11dbbi9 Firmware, Intel Nuc 11 Compute Element Cm11ebc4w Firmware, Intel Nuc 11 Compute Element Cm11ebi38w Firmware, Intel Nuc 11 Compute Element Cm11ebi58w Firmware, Intel Nuc 11 Compute Element Cm11ebi716w Firmware, Intel Nuc 11 Compute Element Cm11ebv58w Firmware, Intel Nuc 11 Compute Element Cm11ebv716w Firmware.

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

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

## Is CVE-2022-38099 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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