CVE-2020-0530
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 buffer restrictions in firmware for Intel(R) NUC may allow an authenticated user to potentially enable escalation of privilege via local access. The list of affected products is provided in intel-sa-00343: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00343.html
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 confidenceImproper buffer restrictions in Intel NUC firmware allow an authenticated local user to potentially escalate privileges. This is a memory corruption vulnerability in the firmware layer that can be exploited by a user with existing system access to gain higher privileges.
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= becfl357.86a.0077= becfl357.86a.0077= hnkbli70.86a.0059= hnkbli70.86a.0059= inwhl357.0036= inwhl357.0036= inwhl357.0036= chaplcel.0047CVSS 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 the Intel NUC modelCheck the physical system label, boot into BIOS (press F2 during startup), or run 'dmidecode -s system-product-name' to determine the exact NUC model number (e.g., Nuc8i7bek, Nuc8i7hnk, Nuc8i7inh, Nuc8i5inh, or Nuc8cchkr)Affected if The model matches one of the affected products listed in the CVE (Nuc8i7bek, Nuc8i7bekqa, Nuc8i7hnk, Nuc8i7hnkqc, Nuc8i7inh, Nuc8i5inh, or Nuc8cchkr)
-
Check the installed firmware versionBoot into BIOS setup (press F2) and locate the BIOS/firmware version under the 'Main' or 'Information' tab, or use the Intel NUC System Update Tool if available, or run 'dmidecode -s bios-version' from the operating systemAffected if The firmware version cannot be determined or is not accessible (firmware version cannot be retrieved)
-
Compare firmware version against affected releasesMatch the installed firmware version string to the affected version(s) for your specific NUC model: Nuc8i7bek/bekqa = becfl357.86a.0077, Nuc8i7hnk/hnkqc = hnkbli70.86a.0059, Nuc8i7inh/i5inh = inwhl357.0036, Nuc8cchkr = chaplcel.0047Affected if The installed firmware version exactly matches one of the affected version strings listed in the CVE
You are affected if you are running an Intel NUC model listed in the CVE with the exact firmware version specified; if your firmware version is different (either older or newer), you may not be affected by this specific vulnerability.
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.
From vendor dataApply the firmware update provided by Intel for affected NUC products via the Intel Security Advisory SA-00343. This requires flashing updated BIOS/firmware to the affected systems.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-0530 — 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-2020-0530 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