# CVE-2023-22330: Information disclosure in Intel(R) NUC BIOS firmware

> A privileged local attacker can exploit uninitialized resources in Intel NUC BIOS firmware to disclose sensitive information.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **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 Oct 2024
- **Also known as:** GHSA-xfqq-wjxw-fghm

## What is CVE-2023-22330?

CVE-2023-22330 is a medium-severity vulnerability in Intel(R) NUC 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

Use of uninitialized resource in some Intel(R) NUC BIOS firmware may allow a privileged user to potentially enable information disclosure via local access.

Weakness: CWE-908 (Use of Uninitialized Resource)

## Which versions are affected by CVE-2023-22330?

It affects 88 products.


Products: 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 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 Kit Nuc11paqi50wa Firmware, Intel Nuc 11 Performance Kit Nuc11paqi70qa Firmware, Intel Nuc 11 Performance Mini Pc Nuc11pahi30z Firmware, Intel Nuc 11 Performance Mini Pc Nuc11pahi3 Firmware, Intel Nuc 11 Performance Mini Pc Nuc11pahi50z Firmware, Intel Nuc 11 Performance Mini Pc Nuc11pahi5 Firmware, Intel Nuc 11 Performance Mini Pc Nuc11pahi70z Firmware and 68 more.

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

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

## Is CVE-2023-22330 being exploited?

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

## Other vulnerabilities in Intel(R) NUC BIOS firmware

- [CVE-2023-22449](https://insights.sbomify.com/CVE-2023-22449/): Privilege escalation in Intel(R) NUC BIOS firmware (high 7.5)
- [CVE-2023-22356](https://insights.sbomify.com/CVE-2023-22356/): Information disclosure in Intel(R) NUC BIOS firmware (medium 6.0)
- [CVE-2023-22444](https://insights.sbomify.com/CVE-2023-22444/): Information disclosure in Intel(R) NUC 13 Extreme Compute Element, Intel(R) NUC 13 Extreme Kit, Intel(R) NUC 11 Performance Kit, Intel(R) NUC 11 Performance Mini PC, Intel(R) NUC Compute Element, Intel(R) NUC Laptop Kit, Intel(R) NUC Pro Kit, Intel(R) NUC Pro Board and Intel(R) NUC Pro Mini PC BIOS firmware (medium 6.0)
- [CVE-2023-34349](https://insights.sbomify.com/CVE-2023-34349/): Race condition in Intel(R) NUC BIOS firmware (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-22330 is a medium-severity vulnerability in Intel(R) NUC 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-22330 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-2023-22330/ (Markdown: https://insights.sbomify.com/CVE-2023-22330/index.md)
```

## Sources

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

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