dbcve.org
Nuc 8 Mainstream G Kit Nuc8i7inh FirmwareOperating system · Intel

CVE-2021-33164

MEDIUM · 6.7 CVSS v3.1 Published 2022-11-11
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
69/100
Remediation priority · Elevated
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 access control in BIOS firmware for some Intel(R) NUCs before version INWHL357.0046 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

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 8 Mainstream G Kit Nuc8i7inh FirmwareOperating system
Affected:< inwhl357.0046
Nuc 8 Mainstream G Mini Pc Nuc8i7inh FirmwareOperating system
Affected:< inwhl357.0046
Nuc 8 Mainstream G Kit Nuc8i5inh FirmwareOperating system
Affected:< inwhl357.0046
Nuc 8 Mainstream G Mini Pc Nuc8i5inh FirmwareOperating system
Affected:< inwhl357.0046

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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

INWHL357.0046 (or later)

  1. Identify your current BIOS version by entering the BIOS setup (F2 during boot) or using Intel's System Diagnostics or System Information utility
  2. Download the BIOS update from Intel's support website for your specific NUC model (Nuc8i7inh or Nuc8i5inh)
  3. Extract the downloaded firmware update file to a USB flash drive formatted as FAT32
  4. Connect the USB drive to the NUC and restart the system
  5. Enter the BIOS setup (F2) and locate the 'Flash BIOS' or 'Update BIOS' option under the 'Security' or 'Advanced' tab
  6. Select the firmware file from the USB drive and initiate the update process
  7. Do not power off the system during the update - the NUC will restart multiple times as part of the update process
  8. After the update completes, enter the BIOS setup to verify the version shows INWHL357.0046 or later
Caveat BIOS settings may be reset to defaults after firmware update - reconfigure any custom boot order, security settings, or overclocking settings as needed

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,600. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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