CVE-2023-28738
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 · uneditedImproper input validation for some Intel NUC BIOS firmware before version JY0070 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 · moderate confidenceImproper input validation vulnerability in Intel NUC BIOS firmware versions prior to JY0070 allows a locally authenticated privileged user to escalate privileges. The vulnerability stems from insufficient validation of certain BIOS input parameters, which could be manipulated to execute code at a higher privilege level than intended. This is a local-only attack requiring existing privileged access.
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= jyglkcpx.0071= jyglkcpx.0071= jyglkcpx.0071= jyglkcpx.0071= jyglkcpx.0071= jyglkcpx.0071CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify your Intel NUC modelLocate the model number sticker on the NUC chassis or check the original packaging. Look for one of these: Nuc7cjysamn, Nuc7cjyhn, Nuc7pjyhn, Nuc7pjyh, Nuc7cjysal, or Nuc7cjyh.Affected if Your model matches one of the listed 7th generation NUC models.
-
Determine the current BIOS versionPower on the NUC and press F2 during boot to enter the BIOS setup, or use Intel's BIOS Update utility from within Windows. Navigate to the Main or Information tab to view the BIOS version string.Affected if The BIOS version displayed matches jyglkcpx.0071 or is an earlier version.
-
Compare against the fixed versionVerify whether your installed BIOS version is earlier than JY0070. The affected versions are those prior to JY0070.Affected if Your BIOS version is jyglkcpx.0071 or any version number lower than JY0070.
-
Confirm local privileged access requirementRecognize that this vulnerability requires an attacker to already have locally authenticated privileged (administrator/root) access to the affected system.Affected if The system has a local privileged user account that could potentially exploit this BIOS input validation flaw.
You are affected if you own a 7th gen Intel NUC (one of the listed models) running BIOS version jyglkcpx.0071 or earlier, which is any version prior to JY0070.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Intel NUC BIOS firmware to version JY0070 or later by downloading the appropriate BIOS update from Intel's support website and following the standard BIOS flashing procedure.
Intel NUC BIOS firmware version JY0070
- Identify your specific NUC model number (e.g., Nuc7cjysamn, Nuc7cjyhn, etc.)
- Visit the Intel Support website (intel.com/support) and navigate to the drivers and support section for Intel NUC products
- Search for your specific NUC model and locate the BIOS/firmware downloads section
- Download the BIOS update file version JY0070 (or latest available) for your specific model
- Review the download page for any specific update instructions or requirements
- Run the BIOS update utility (typically a .exe file) or copy the update to a USB drive as instructed
- Follow the on-screen prompts to initiate the BIOS update - do not interrupt the process
- Allow the system to complete the update and restart automatically if required
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28738 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-28738 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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