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

> A privileged local attacker can exploit improper buffer restrictions in Intel NUC BIOS firmware to disclose sensitive information.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:H/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:** 14 Nov 2023
- **Updated:** 14 Aug 2024
- **Also known as:** GHSA-xmm7-2j6p-p24v

## What is CVE-2023-40220?

CVE-2023-40220 is a medium-severity vulnerability in Intel(R) NUC BIOS firmware, published on 14 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper buffer restrictions in some Intel(R) NUC BIOS firmware may allow a privileged user to potentially enable information disclosure via local access.

Weakness: CWE-92 (DEPRECATED: Improper Sanitization of Custom Special Characters)

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

It affects 2 products.


Products: Intel Nuc6cayh Firmware, Intel Nuc6cays Firmware.

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

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

## Is CVE-2023-40220 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-40220 is a medium-severity vulnerability in Intel(R) NUC BIOS firmware, published on 14 Nov 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-40220 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-40220/ (Markdown: https://insights.sbomify.com/CVE-2023-40220/index.md)
```

## Sources

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

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