# CVE-2022-32582: Missing authorization in Intel(R) NUC Boards, Intel(R) NUC 11 Performance Kit, Intel(R) NUC 11 Performance Mini PC, Intel(R) NUC Pro Compute Element

> A privileged local user can cause a denial of service on Intel NUC devices due to improper access control in the firmware.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:N/I:N/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-p76v-vqrf-mq5q

## What is CVE-2022-32582?

CVE-2022-32582 is a medium-severity missing authorization vulnerability in Intel(R) NUC Boards, Intel(R) NUC 11 Performance Kit, Intel(R) NUC 11 Performance Mini PC, Intel(R) NUC Pro 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 access control in firmware for some Intel(R) NUC Boards, Intel(R) NUC 11 Performance Kit, Intel(R) NUC 11 Performance Mini PC, Intel(R) NUC Pro Compute Element may allow a privileged user to potentially enable denial of service via local access.

Weakness: CWE-284 (Improper Access Control)

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

It affects 39 products.


Products: Intel Nuc 11 Performance Kit Nuc11pahi30z Firmware, Intel Nuc 11 Performance Kit Nuc11pahi3 Firmware, Intel Nuc 11 Performance Kit Nuc11pahi50z Firmware, Intel Nuc 11 Performance Kit Nuc11pahi5 Firmware, Intel Nuc 11 Performance Kit Nuc11pahi70z Firmware, Intel Nuc 11 Performance Kit Nuc11pahi7 Firmware, Intel Nuc 11 Performance Kit Nuc11paki3 Firmware, Intel Nuc 11 Performance Kit Nuc11paki5 Firmware, Intel Nuc 11 Performance Kit Nuc11paki7 Firmware, Intel Nuc 11 Performance Mini Pc Nuc11paqi50wa Firmware, Intel Nuc 11 Performance Mini Pc Nuc11paqi70qa Firmware, Intel Nuc 11 Pro Board Nuc11tnbi30z Firmware, Intel Nuc 11 Pro Board Nuc11tnbi3 Firmware, Intel Nuc 11 Pro Board Nuc11tnbi50z Firmware, Intel Nuc 11 Pro Board Nuc11tnbi5 Firmware, Intel Nuc 11 Pro Board Nuc11tnbi70z Firmware, Intel Nuc 11 Pro Board Nuc11tnbi7 Firmware, Intel Nuc 11 Pro Kit Nuc11tnhi30l Firmware, Intel Nuc 11 Pro Kit Nuc11tnhi30p Firmware, Intel Nuc 11 Pro Kit Nuc11tnhi30z Firmware and 19 more.

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

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

## Is CVE-2022-32582 being exploited?

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

## Other vulnerabilities in Intel(R) NUC Boards, Intel(R) NUC 11 Performance Kit, Intel(R) NUC 11 Performance Mini PC, Intel(R) NUC Pro Compute Element

- [CVE-2022-33176](https://insights.sbomify.com/CVE-2022-33176/): Privilege escalation in Intel(R) NUC 11 Performance kits and Intel(R) NUC 11 Performance Mini PCs (high 8.2)
- [CVE-2023-29500](https://insights.sbomify.com/CVE-2023-29500/): Information disclosure in Intel(R) NUCs (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-32582 is a medium-severity missing authorization vulnerability in Intel(R) NUC Boards, Intel(R) NUC 11 Performance Kit, Intel(R) NUC 11 Performance Mini PC, Intel(R) NUC Pro 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-32582 in the wild and no public exploit code.

Affected product: Intel(R) NUC Boards, Intel(R) NUC 11 Performance Kit, Intel(R) NUC 11 Performance Mini PC, Intel(R) NUC Pro 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-32582/ (Markdown: https://insights.sbomify.com/CVE-2022-32582/index.md)
```

## Sources

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

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