# CVE-2023-32617: Privilege escalation in Intel(R) NUC Rugged Kit, Intel(R) NUC Kit and Intel(R) Compute Element BIOS firmware

> A privileged local attacker can escalate privileges via improper input validation in Intel NUC and Compute Element BIOS firmware.

- **Severity:** High 8.2 (`CVSS:3.1/AV:L/AC:L/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 Aug 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-5pjj-4p22-m4gr

## What is CVE-2023-32617?

CVE-2023-32617 is a high-severity vulnerability in Intel(R) NUC Rugged Kit, Intel(R) NUC Kit and Intel(R) Compute Element BIOS firmware, 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 some Intel(R) NUC Rugged Kit, Intel(R) NUC Kit and Intel(R) Compute Element 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-2023-32617?

It affects 23 products.


Products: Intel Compute Stick Stk2mv64cc Firmware, Intel Nuc 7 Enthusiast Nuc7i7bnhxg Firmware, Intel Nuc 7 Enthusiast Nuc7i7bnkq Firmware, Intel Nuc 7 Home Nuc7i3bnhxf Firmware, Intel Nuc 7 Home Nuc7i5bnhxf Firmware, Intel Nuc 7 Home Nuc7i5bnkp Firmware, Intel Nuc 8 Rugged Board Nuc8cchbn Firmware, Intel Nuc 8 Rugged Kit Nuc8cchkr Firmware, Intel Nuc 8 Rugged Kit Nuc8cchkrn Firmware, Intel Nuc Board Nuc7i3bnb Firmware, Intel Nuc Board Nuc7i5bnb Firmware, Intel Nuc Board Nuc7i7bnb Firmware, Intel Nuc Board Nuc8cchb Firmware, Intel Nuc Kit Nuc6cayh Firmware, Intel Nuc Kit Nuc6cays Firmware, Intel Nuc Kit Nuc7i3bnh Firmware, Intel Nuc Kit Nuc7i3bnhx1 Firmware, Intel Nuc Kit Nuc7i3bnk Firmware, Intel Nuc Kit Nuc7i5bnh Firmware, Intel Nuc Kit Nuc7i5bnhx1 Firmware and 3 more.

## How do I fix CVE-2023-32617?

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

## Is CVE-2023-32617 being exploited?

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

## Other vulnerabilities in Intel(R) NUC Rugged Kit, Intel(R) NUC Kit and Intel(R) Compute Element BIOS firmware

- [CVE-2022-32766](https://insights.sbomify.com/CVE-2022-32766/): Privilege escalation in Intel(R) BIOS firmware (high 7.2)
- [CVE-2023-25771](https://insights.sbomify.com/CVE-2023-25771/): Missing authorization in Intel(R) NUC BIOS firmware (medium 5.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-32617 and fix it if it is affected.

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

Affected product: Intel(R) NUC Rugged Kit, Intel(R) NUC Kit and Intel(R) Compute Element 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-2023-32617/ (Markdown: https://insights.sbomify.com/CVE-2023-32617/index.md)
```

## Sources

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

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