dbcve.org
Nuc 11 Pro Kit Nuc11tnhi70z FirmwareOperating system · Intel

CVE-2022-37334

HIGH · 7.8 CVSS v3.1 Published 2022-11-11
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

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 initialization in BIOS firmware for some Intel(R) NUC 11 Pro Kits and Intel(R) NUC 11 Pro Boards before version TNTGL357.0064 may allow an authenticated 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

A detailed technical summary for this CVE is being prepared.

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 11 Pro Kit Nuc11tnhi70z FirmwareOperating system
Affected:< tntgl357.0064
Nuc 11 Pro Kit Nuc11tnki70z FirmwareOperating system
Affected:< tntgl357.0064
Nuc 11 Pro Kit Nuc11tnki30z FirmwareOperating system
Affected:< tntgl357.0064
Nuc 11 Pro Kit Nuc11tnhi30z FirmwareOperating system
Affected:< tntgl357.0064
Nuc 11 Pro Kit Nuc11tnki50z FirmwareOperating system
Affected:< tntgl357.0064
Nuc 11 Pro Kit Nuc11tnhi50z FirmwareOperating system
Affected:< tntgl357.0064
Nuc 11 Pro Board Nuc11tnbi30z FirmwareOperating system
Affected:< tntgl357.0064
Nuc 11 Pro Board Nuc11tnbi50z FirmwareOperating system
Affected:< tntgl357.0064

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

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
Patch available Apply the vendor patch
Vendor patch www.intel.com →
Recommended fix High confidence

TNTGL357.0064

  1. 1. Visit Intel's support website and search for your specific NUC model (e.g., Nuc11tnhi70z)
  2. 2. Navigate to the Drivers & Software section for your model
  3. 3. Download the BIOS update file (TNTGL357.0064 or later) from Intel's official site
  4. 4. Extract the downloaded file and run the BIOS update utility, or copy the .bio file to a USB flash drive
  5. 5. Restart the computer and boot into the BIOS setup (press F2 during boot)
  6. 6. Locate the 'BIOS Update' or 'Flash BIOS' option in the advanced or security settings
  7. 7. Select the update file from the USB drive or run the utility from within Windows
  8. 8. Wait for the BIOS update process to complete - do not power off the system during the update
Caveat BIOS updates carry a risk of system failure if interrupted; ensure stable power connection and do not power off during the flash process

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

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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