# CVE-2022-36349: Misconfiguration in Intel(R) NUC Boards and Intel(R) NUC Kits

> An authenticated local user can cause a denial of service in Intel NUC firmware due to insecure default variable initialization.

- **Severity:** Medium 5.2 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Nov 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-cc55-85c3-4v7g

## What is CVE-2022-36349?

CVE-2022-36349 is a medium-severity vulnerability in Intel(R) NUC Boards and Intel(R) NUC Kits, published on 11 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insecure default variable initialization in BIOS firmware for some Intel(R) NUC Boards and Intel(R) NUC Kits before version MYi30060 may allow an authenticated user to potentially enable denial of service via local access.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

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

It affects 2 products.


Products: Intel Nuc Board Nuc5i3mybe Firmware, Intel Nuc Kit Nuc5i3myhe Firmware.

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

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

## Is CVE-2022-36349 being exploited?

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

## Other vulnerabilities in Intel(R) NUC Boards and Intel(R) NUC Kits

- [CVE-2022-36370](https://insights.sbomify.com/CVE-2022-36370/): Privilege escalation in Intel(R) NUC Boards and Intel(R) NUC Kits (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36349 is a medium-severity vulnerability in Intel(R) NUC Boards and Intel(R) NUC Kits, published on 11 Nov 2022. 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-36349 in the wild and no public exploit code.

Affected product: Intel(R) NUC Boards and Intel(R) NUC Kits. 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-36349/ (Markdown: https://insights.sbomify.com/CVE-2022-36349/index.md)
```

## Sources

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

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