dbcve.org
Nuc 10 Performance Kit Nuc10i7fnhn FirmwareOperating system · Intel

CVE-2022-36789

HIGH · 7.8 CVSS v3.1 Published 2022-11-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper access control in BIOS firmware for some Intel(R) NUC 10 Performance Kits and Intel(R) NUC 10 Performance Mini PCs before version FNCML357.0053 may allow a privileged user to potentially enable escalation of privilege via local access.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Improper access control in BIOS firmware for Intel NUC 10 devices allows a privileged local user to escalate their privileges. This is a firmware-level vulnerability in the BIOS access control mechanisms that exists prior to version FNCML357.0053.

MitigationUpdate the BIOS firmware on affected Intel NUC 10 devices to version FNCML357.0053 or later. This is a local-only attack requiring existing privileged access, so network-based controls provide limited benefit.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Nuc 10 Performance Kit Nuc10i7fnhn FirmwareOperating system
Affected:< fncml357.0053
Nuc 10 Performance Kit Nuc10i5fnkn FirmwareOperating system
Affected:< fncml357.0053
Nuc 10 Performance Kit Nuc10i5fnhn FirmwareOperating system
Affected:< fncml357.0053
Nuc 10 Performance Kit Nuc10i7fnkn FirmwareOperating system
Affected:< fncml357.0053
Nuc 10 Performance Kit Nuc10i3fnhn FirmwareOperating system
Affected:< fncml357.0053
Nuc 10 Performance Kit Nuc10i3fnkn FirmwareOperating system
Affected:< fncml357.0053
Nuc 10 Performance Mini Pc Nuc10i5fnhja FirmwareOperating system
Affected:< fncml357.0053
Nuc 10 Performance Kit Nuc10i3fnhf FirmwareOperating system
Affected:< fncml357.0053

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify your Intel NUC model
    Check the product label on the device chassis or run 'wmic computersystem get model' on Windows or 'sudo dmidecode -s system-product-name' on Linux
    Affected if The model is not one of the listed Intel NUC 10 variants (Nuc10i7fnhn, Nuc10i5fnkn, Nuc10i5fnhn, Nuc10i7fnkn, Nuc10i3fnhn, Nuc10i3fnkn, Nuc10i5fnhja, Nuc10i3fnhf)
  2. Determine the current BIOS firmware version
    During boot, press F2 to enter BIOS setup and view the firmware version on the main screen, or run 'wmic bios get smbiosbiosversion' on Windows or 'sudo dmidecode -s bios-version' on Linux
    Affected if The reported BIOS version is below fncml357.0053 (for example, fncml357.0052 or earlier)
  3. Confirm the BIOS version format matches Intel's naming
    Verify the firmware version string starts with 'fncml357' - Intel uses this naming convention for NUC 10 firmware updates
    Affected if The version string exists but does not follow the fncml357.xxxx format or cannot be determined

Your Intel NUC 10 device is affected if it is one of the listed models and its BIOS firmware version is lower than fncml357.0053.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the BIOS firmware on affected Intel NUC 10 devices to version FNCML357.0053 or later. This is a local-only attack requiring existing privileged access, so network-based controls provide limited benefit.

Recommended fix High confidence

FNCML357.0053

  1. 1. Identify the exact Intel NUC 10 model number (e.g., Nuc10i7fnhn, Nuc10i5fnkn, etc.) from the affected product list.
  2. 2. Visit the Intel NUC Support page (www.intel.com) and locate the BIOS download page for your specific NUC model.
  3. 3. Download the BIOS update file version FNCML357.0053 or later for your specific model.
  4. 4. Follow Intel's BIOS update instructions, which typically involve running the update utility from Windows or creating a USB recovery drive.
  5. 5. Ensure the system is connected to AC power during the BIOS update process and do not power off until the update completes.
  6. 6. After the update, verify the BIOS version shows FNCML357.0053 or later in the BIOS setup utility.
Caveat BIOS updates carry a risk of system damage if interrupted; ensure stable power and follow update instructions precisely

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nuc 10 Performance Kit Nuc10i7fnhn Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-36789 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-36789 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data