dbcve.org
Nuc10i3fnh FirmwareOperating system · Intel

CVE-2022-37327

MEDIUM · 5.5 CVSS v3.1 Published 2023-05-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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 input validation in BIOS firmware for 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 may allow a privileged user to enable information disclosure 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 · high confidence

This vulnerability involves improper input validation in the BIOS firmware of various Intel NUC devices. A privileged user with local access can exploit this input validation flaw to enable information disclosure. The CVSS 5.5 score indicates moderate severity with local attack vector and low attack complexity.

MitigationApply the Intel-provided BIOS firmware update for affected NUC products. Since this requires privileged local access, ensure proper access controls and monitor for unauthorized local access to affected systems.

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
Nuc10i3fnh FirmwareOperating system
Affected:< fncml357.0059
Nuc10i3fnhf FirmwareOperating system
Affected:< fncml357.0059
Nuc10i3fnhfa FirmwareOperating system
Affected:< fncml357.0059
Nuc10i3fnhja FirmwareOperating system
Affected:< fncml357.0059
Nuc10i3fnhn FirmwareOperating system
Affected:< fncml357.0059
Nuc10i3fnk FirmwareOperating system
Affected:< fncml357.0059
Nuc10i3fnkn FirmwareOperating system
Affected:< fncml357.0059
Nuc10i5fnh FirmwareOperating system
Affected:< fncml357.0059

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
None
Availability
None

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

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 Intel NUC model
    Check the system model by looking at the physical chassis label, or run 'wmic computersystem get model' in Windows or 'dmidecode -s system-product-name' in Linux
    Affected if System model matches NUC10i3fnh, NUC10i3fnhf, NUC10i3fnhfa, NUC10i3fnhja, NUC10i3fnhn, NUC10i3fnk, NUC10i3fnkn, or NUC10i5fnh variants
  2. Check BIOS firmware version
    Enter BIOS setup by pressing F2 during boot, navigate to Main or Information page to view BIOS version, or use 'wmic bios get smbiosbiosversion' command in Windows, or 'dmidecode -s bios-version' in Linux
    Affected if Firmware version displayed is fncml357.0059 or lower
  3. Compare version against patched release
    Review the installed firmware version number against the fixed version fncml357.0059 - note that versions with numbers less than 0059 (such as 0058, 0057, etc.) are vulnerable
    Affected if Installed version string numeric portion is less than 0059 (for example, 0058, 0057, 0046)

System is affected if it is an Intel NUC10i3 or NUC10i5 variant with BIOS firmware version lower than fncml357.0059, and the attacker has privileged local access to the device.

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

Apply the Intel-provided BIOS firmware update for affected NUC products. Since this requires privileged local access, ensure proper access controls and monitor for unauthorized local access to affected systems.

Recommended fix High confidence

fncml357.0059

  1. Identify your specific Intel NUC model from the affected list (Nuc10i3fnh, Nuc10i3fnhf, Nuc10i3fnhfa, Nuc10i3fnhja, Nuc10i3fnhn, Nuc10i3fnk, Nuc10i3fnkn, or Nuc10i5fnh)
  2. Navigate to Intel's support website and locate the BIOS update page for your specific NUC model
  3. Download the BIOS firmware version fncml357.0059 or later for your model
  4. Review Intel's BIOS update instructions for your specific NUC (typically involves either entering BIOS setup with F2 during boot or using Intel's Firmware Update Utility)
  5. Create a bootable USB or use the Intel update method as specified in the instructions
  6. Perform the BIOS update following Intel's documented procedure, ensuring the system remains powered throughout the process
  7. After the update completes, verify the BIOS version has been updated to fncml357.0059 or later

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

Fix this in Nuc10i3fnh Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-37327 — 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-37327 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