# CVE-2022-31477: Information disclosure in Intel(R) NUC BIOS firmware

> A privileged local attacker can exploit improper BIOS initialization to disclose sensitive information on Intel NUC devices.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 May 2023
- **Updated:** 27 Jan 2025
- **Also known as:** GHSA-q7r2-c6mw-rgwr

## What is CVE-2022-31477?

CVE-2022-31477 is a medium-severity vulnerability in Intel(R) NUC BIOS firmware, published on 10 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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

Weakness: CWE-665 (Improper Initialization)

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

It affects 35 products.


Products: Intel Cm11ebc4w Firmware, Intel Cm11ebi38w Firmware, Intel Cm11ebi58w Firmware, Intel Cm11ebi716w Firmware, Intel Lapbc510 Firmware, Intel Lapbc710 Firmware, Intel Lapkc51e Firmware, Intel Lapkc71e Firmware, Intel Lapkc71f Firmware, Intel Nuc11btmi7 Firmware, Intel Nuc11btmi9 Firmware, Intel Nuc11dbbi7 Firmware, Intel Nuc11dbbi9 Firmware, Intel Nuc11pahi30z Firmware, Intel Nuc11pahi3 Firmware, Intel Nuc11pahi50z Firmware, Intel Nuc11pahi5 Firmware, Intel Nuc11pahi70z Firmware, Intel Nuc11pahi7 Firmware, Intel Nuc11paki3 Firmware and 15 more.

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

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

## Is CVE-2022-31477 being exploited?

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

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

- [CVE-2022-36339](https://insights.sbomify.com/CVE-2022-36339/): Privilege escalation in Intel(R) NUC 8 Compute Element, Intel(R) NUC 11 Compute Element, Intel(R) NUC 12 Compute Element (high 7.5)
- [CVE-2022-37327](https://insights.sbomify.com/CVE-2022-37327/): Information disclosure in Intel(R) NUC, Intel(R) NUC Performance Kit, Intel(R) NUC Performance Mini PC, Intel(R) NUC 8 Compute Element, Intel(R) NUC Pro Kit, Intel(R) NUC Pro Board, Intel(R) NUC 11 Compute Element, Intel(R) NUC 12 Compute Element, Intel(R) NUC Extreme, Intel(R) NUC 12 Extreme Compute Element, Intel(R) NUC Laptop Kit, Intel(R) NUC Enthusiast, Intel(R) NUC Essential, Intel(R) NUC Laptop Kit, Intel(R) NUC Extreme Compute Element, Intel(R) NUC Boards, Intel(R) NUC Pro Compute Element, Intel(R) NUC Rugged (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-31477 is a medium-severity vulnerability in Intel(R) NUC BIOS firmware, published on 10 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-31477 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-2022-31477/ (Markdown: https://insights.sbomify.com/CVE-2022-31477/index.md)
```

## Sources

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

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