CVE-2016-8103
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 · uneditedSMM call out in all Intel Branded NUC Kits allows a local privileged user to access the System Management Mode and take full control of the platform.
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 confidenceIntel NUC kits contain a vulnerability allowing a local privileged user to trigger a callout to System Management Mode (SMM), a high-privilege x86 processor mode operating below the OS. This enables the attacker to escape their current privilege context and gain firmware-level control of the platform.
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<= ccsklm5v.86a= ccsklm30.86a<= ccsklm30.86a<= scchtax5.86a<= kyskli70.86a<= pybwcel.86a<= fybyt10h.86a<= mybdwi5v.86a<= mybdwi30.86a<= rybdwi35.86a<= syskli35.86a<= scchtax5.86aCVSS 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.0/AV:L/AC:L/PR:H/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 Intel NUC modelRun 'dmidecode -s system-product-name' or check system documentation/labels for Intel NUCAffected if System is not an Intel NUC kit (this CVE only affects specific Intel NUC models)
-
Determine BIOS versionRun 'dmidecode -s bios-version' to retrieve the current BIOS firmware version stringAffected if Unable to retrieve BIOS version (firmware may be locked or inaccessible)
-
Compare against affected City Bios versionsCompare your BIOS version to these affected strings: ccsklm5v.86a, ccsklm30.86a, scchtax5.86a - note that <= versions before/including these are affected, = ccsklm30.86a is affectedAffected if Your BIOS version matches or precedes any of: ccsklm5v.86a, ccsklm30.86a, scchtax5.86a (exact match for ccsklm30.86a, any version up to these)
-
Compare against affected Canyon Bios versionsCompare your BIOS version to these affected strings: kyskli70.86a, pybwcel.86a, fybyt10h.86a, mybdwi5v.86a, mybdwi30.86a, rybdwi35.86a - versions <= these are affectedAffected if Your BIOS version matches or precedes any of: kyskli70.86a, pybwcel.86a, fybyt10h.86a, mybdwi5v.86a, mybdwi30.86a, rybdwi35.86a
-
Compare against affected Swift Canyon and Citry Bios versionsCompare your BIOS version to: syskli35.86a (Swift Canyon, <= affected), scchtax5.86a (Citry, <= affected)Affected if Your BIOS version is at or before syskli35.86a (Swift Canyon model) or scchtax5.86a (Citry model)
You are affected if you are running an Intel NUC with a BIOS version that matches or is older than any of the specific version strings listed for City, Canyon, Swift Canyon, or Citry models, and an unpatched local privileged user scenario exists.
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 Intel firmware updates for affected NUC kits; if patches are unavailable, implement strict physical access controls and network isolation to limit exposure to local privileged users.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-8103 — 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-2016-8103 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