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

CVE-2023-28722

HIGH · 7.8 CVSS v3.1 Published 2024-01-19
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 buffer restrictions for some Intel NUC BIOS firmware before version IN0048 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 · high confidence

Intel NUC BIOS firmware before version IN0048 contains improper buffer restrictions that could allow a privileged local user to exploit buffer overflow or similar memory corruption to escalate privileges. The vulnerability requires local access and an already-privileged user account.

MitigationUpdate Intel NUC BIOS firmware to version IN0048 or later following Intel's official firmware update procedures for the specific NUC model.

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

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 NUC model and BIOS version
    On Windows, run 'msinfo32' or 'systeminfo' in Command Prompt and look for 'BIOS Version' and 'System Model'. On Linux, run 'sudo dmidecode -s bios-version' and 'sudo dmidecode -s system-product-name'.
    Affected if The model is Intel NUC 8 Mainstream G Kit (Nuc8i5inh or Nuc8i7inh) and the BIOS version is inwhl357.0049 or any version earlier than IN0048
  2. Confirm firmware version format matches vulnerable release
    Locate the BIOS version string in the system information output. Intel NUC firmware versions follow a format like 'inwhl357.0049' where 'inwhl357' is the firmware family and '0049' is the build number.
    Affected if The firmware version string is exactly 'INWHL357.0049' (case-insensitive match)
  3. Verify system is not patched to IN0048 or later
    Compare your detected BIOS version against the fixed release IN0048. On Intel NUCs, the BIOS version is typically displayed in the BIOS setup (press F2 at boot) under 'Advanced' or 'Main' settings, or via the Intel NUC Software Studio/Intel Driver & Support Assistant.
    Affected if The installed BIOS version is lower than IN0048 (for example, INWHL357.0049 or earlier builds in the same family)
  4. Confirm local privileged access requirement
    The vulnerability requires an attacker to already have privileged local access (administrator/root). Verify whether untrusted local user accounts exist on the system with elevated privileges.
    Affected if The system has local user accounts with administrative or root privileges beyond the primary administrator, and the BIOS version is among the affected versions listed

A system is affected if it is an Intel NUC 8 Mainstream G Kit (Nuc8i5inh or Nuc8i7inh) running BIOS firmware version inwhl357.0049 or any version earlier than IN0048, with local privileged user accounts present.

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 Intel NUC BIOS firmware to version IN0048 or later following Intel's official firmware update procedures for the specific NUC model.

Recommended fix High confidence

BIOS firmware version IN0048 or later

  1. Navigate to Intel's support website and download the BIOS firmware update version IN0048 for your specific NUC model (Nuc8i5inh or Nuc8i7inh)
  2. Verify the downloaded file checksum matches the provided value from Intel
  3. Read and follow Intel's BIOS update instructions carefully - typically involves running the BIOS update utility from Windows or creating a USB recovery drive
  4. Ensure the system is connected to a stable power source throughout the update process - do not power off or restart during the update
  5. After the update completes, the system will restart automatically; verify the BIOS version shows IN0048 or later
Caveat BIOS updates carry risk if interrupted; ensure stable power and follow all Intel instructions precisely

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

Fix this in Nuc 8 Mainstream G Kit Nuc8i5inh Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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