Safeguard
Vulnerability Analysis•

CVE-2023-28738: High Input Validation Flaw in Intel NUC 7 BIOS

CVE-2023-28738 is an input validation flaw in Intel NUC 7 Essential BIOS before JY0070. Update the BIOS to JYGLKCPX.0071 as listed by Intel.

Safeguard Security Team
3 min read

CVE-2023-28738 is an improper input validation flaw in the BIOS of Intel NUC 7 Essential and NUC Kit models. It may let a privileged user escalate privilege through local access. NVD and Intel score it 7.5, High. Update the BIOS to JYGLKCPX.0071.

What's affected

Intel advisory INTEL-SA-01009 lists this CVE as follows.

  • Affected: NUC 7 Essential and NUC Kit BIOS versions before JY0070.
  • Product families: NUC7CJYSAMN, NUC7CJYHN, NUC7PJYHN, NUC7PJYH, NUC7CJYSAL and NUC7CJYH.
  • Fixed BIOS: JYGLKCPX.0071.
  • Intel's score: 7.5, High (vector CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H).

The NVD record agrees with Intel on the score, so there is no severity conflict. All three CVEs in this advisory need local access and a privileged user, according to the vectors.

How to check if you're exposed

Read the BIOS version and compare it with the fixed one. Three ways to do it:

Get-CimInstance Win32_BIOS | Select-Object SMBIOSBIOSVersion

That is PowerShell on Windows. On Linux, run sudo dmidecode -s bios-version. You can also press F2 at start up and read the version on the BIOS setup main screen.

Compare the result with the fixed build listed in this post. Intel's version strings use a prefix for the board family and a number, so compare the number against the one in the advisory.

What to do now

  1. Update the BIOS to JYGLKCPX.0071 or newer, using the instructions and download that Intel links from the advisory.
  2. Intel's advisory says to check its NUC transition page after January 15, 2024 for updates on affected products, so confirm the download source there if the links have moved.
  3. Restrict administrator access on affected machines, since the attack needs a privileged user.
  4. Set a BIOS or firmware password where your policy allows it, so settings cannot be changed casually.
  5. Add the machine and its BIOS version to your asset list.

Why it matters

The record lists CWE-20 (Improper Input Validation) and CWE-116 (Improper Encoding or Escaping of Output). In Intel's words this is improper input validation in BIOS firmware, and it may let a privileged user escalate privilege with local access. The vector shows a changed scope with high impact on confidentiality, integrity and availability, which is why the score reaches High.

Scope change means a flaw in one component affects resources beyond its own security boundary. For firmware, that boundary is the operating system and everything above it. A privileged local attacker could affect the platform itself, and not only the account they started with.

Intel's advisory covers three NUC CVEs together. If you have mixed NUC generations, handle them in one pass using the table in the advisory.

Quick check

Why is a local flaw rated High?

Because the scope changes and the impact on confidentiality, integrity and availability is high. The privilege and complexity requirements keep it from scoring higher.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.