CVE-2016-8103
First published: Thu Dec 08 2016(Updated: )
SMM 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.
Credit: secure@intel.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Intel City BIOS | <=ccsklm5v.86a | |
| Intel Compute Stick STK2M3W64CC Firmware | ||
| Intel Canyon BIOS | <=kyskli70.86a | |
| Intel NUC 6i7KYB | ||
| Intel Canyon BIOS | <=pybwcel.86a | |
| Intel NUC 5CPYH | ||
| Intel nuc5pgyh | ||
| Intel NUC 5PPYH | ||
| Intel City BIOS | =ccsklm30.86a | |
| Intel Compute Stick STK2MV64CC | ||
| Intel Canyon BIOS | <=fybyt10h.86a | |
| Intel NUC Kit DN2820FYKH | ||
| Intel City BIOS | <=ccsklm30.86a | |
| Intel Canyon BIOS | <=syskli35.86a | |
| Intel NUC 6i3SYB | ||
| Intel NUC6i5SYB | ||
| Intel City BIOS | <=scchtax5.86a | |
| Intel STK1AW32SC | ||
| Intel Canyon BIOS | <=mybdwi5v.86a | |
| Intel NUC board nuc5i3mybe | ||
| Intel Canyon BIOS | <=mybdwi30.86a | |
| Intel City BIOS | <=scchtax5.86a | |
| Intel STK1A32SC | ||
| Intel Canyon BIOS | <=rybdwi35.86a | |
| Intel NUC 5i3RYB | ||
| Intel NUC 5i5RYB | ||
| Intel NUC 5i7RYH |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-8103?
CVE-2016-8103 is classified as a high severity vulnerability due to the potential for local privileged users to gain full control over the platform.
How do I fix CVE-2016-8103?
To fix CVE-2016-8103, users should update their Intel systems with the latest firmware provided by Intel that addresses this vulnerability.
What impacts does CVE-2016-8103 have on affected Intel systems?
CVE-2016-8103 allows local privileged users to access the System Management Mode, potentially leading to full control of the affected systems.
Which Intel products are affected by CVE-2016-8103?
CVE-2016-8103 affects various Intel Branded NUC Kits and City and Canyon BIOS versions up to specified releases.
Is there a workaround for CVE-2016-8103 while waiting for a fix?
Currently, the best approach is to apply the firmware update as no specific workaround is provided for CVE-2016-8103.
- agent/type
- agent/references
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/weakness
- agent/last-modified-date
- agent/author
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/intel
- canonical/intel city bios
- version/intel city bios/ccsklm5v.86a
- canonical/intel compute stick stk2m3w64cc firmware
- canonical/intel canyon bios
- version/intel canyon bios/kyskli70.86a
- canonical/intel nuc 6i7kyb
- version/intel canyon bios/pybwcel.86a
- canonical/intel nuc 5cpyh
- canonical/intel nuc5pgyh
- canonical/intel nuc 5ppyh
- version/intel city bios/ccsklm30.86a
- canonical/intel compute stick stk2mv64cc
- version/intel canyon bios/fybyt10h.86a
- canonical/intel nuc kit dn2820fykh
- version/intel canyon bios/syskli35.86a
- canonical/intel nuc 6i3syb
- canonical/intel nuc6i5syb
- version/intel city bios/scchtax5.86a
- canonical/intel stk1aw32sc
- version/intel canyon bios/mybdwi5v.86a
- canonical/intel nuc board nuc5i3mybe
- version/intel canyon bios/mybdwi30.86a
- canonical/intel stk1a32sc
- version/intel canyon bios/rybdwi35.86a
- canonical/intel nuc 5i3ryb
- canonical/intel nuc 5i5ryb
- canonical/intel nuc 5i7ryh