CVE-2016-8103: Medium severity intel city bios vulnerability

Published Dec 8, 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.

Affected Software

27 affected components
Intel City Bios<=ccsklm5v.86a
Intel Stk2m3w64cc
Intel Canyon Bios<=kyskli70.86a
Intel Nuc6i7kyb
Intel Canyon Bios<=pybwcel.86a
Intel Nuc5cpyh
Intel Nuc5pgyh
Intel Nuc5ppyh
Intel City Bios=ccsklm30.86a
Intel Stk2mv64cc
Intel Canyon Bios<=fybyt10h.86a
Intel Dn2820fyb
Intel City Bios<=ccsklm30.86a
Intel Swift Canyon Bios<=syskli35.86a
Intel Nuc6i3syb
Intel Nuc6i5syb
Intel Citry Bios<=scchtax5.86a
Intel Stk1aw32sc
Intel Canyon Bios<=mybdwi5v.86a
Intel Nuc5i3mybe
Intel Canyon Bios<=mybdwi30.86a
Intel City Bios<=scchtax5.86a
Intel Stk1a32sc
Intel Canyon Bios<=rybdwi35.86a
Intel Nuc5i3ryb
Intel Nuc5i5ryb
Intel Nuc5i7rykh

Event History

Dec 8, 2016
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
DescriptionWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203