The latest security information on Intel® products.

DCI Policy Update

Intel ID:
INTEL-SA-00127
Product family:
5th and 6th generation Intel® Xeon® Processor E3 family, Intel® Xeon® Scalable processors, and Intel® Xeon® Processor D family
Impact of vulnerability:
Information Disclosure, Escalation of Privilege
Severity rating:
Important
Original release:
07/09/2018
Last revised:
07/09/2018

Summary:

Intel is releasing Direct Connect Interface (DCI) policy update.

Description:

Existing UEFI setting restrictions for DCI (Direct Connect Interface) in 5th and 6th generation Intel® Xeon® Processor E3 Family, Intel® Xeon® Scalable processors, and Intel® Xeon® Processor D Family can potentially allow a limited physical presence attacker to access platform secrets via debug interfaces.

Affected products:

•    Note:  Client platforms are not included in the following table, because all client platforms are expected to have EFI Secure Boot enabled & the UEFI Variable controlling DCI set to default disabled.

Potentially Affected Platform

Mitigated Platform sample code

Code Name Purley:

Intel® Xeon® Scalable processors

Available in Post Launch Release 7

or later on VIP @ https://platformsw.intel.com

Code Name Greenlow:

Intel® Xeon® Processor E3 v6 Family (Kaby Lake)

Intel® Xeon® Processor E3 v5 Family (Skylake)

Perform a code review based on TA content and remove the vulnerability as necessary. 

Code Name Bakerville:

Intel® Xeon® Processor D Family (Skylake-D)

Available in Post Launch Release 2

or later on VIP @ https://platformsw.intel.com

Code Name Harrisonville:

Intel® Atom ™ Processor C Series (Denverton)

Perform a code review based on TA content and remove the vulnerability as necessary. 

 

Recommendations:

Intel highly recommends that all potentially affected platforms modify the DCI policy such that DCI control is disabled.  Below are references to Purley, Bakerville, and Greenlow codebases.

•    Sample Code Filename:

        Greenlow filename:  PeiPchPolicyDebugLib.c

        Purley/Bakerville filename:  PeiPchPolicyUpdate.c

•    Code to change in Sample Code File:

        PchPolicy->DciConfig.DciEn  = 0;

        PchPolicy->DciConfig.DciAutoDetect = 0;

Acknowledgements:

Intel would like to thank Jesse Michael from Eclypsium for reporting this issue and working with us on coordinated disclosure.

Revision History

Revision Date Description
1.0 07/09/2018 Initial Release

CVE Name: CVE-2018-3652

Legal Notices and Disclaimers

Intel provides these materials as-is, with no express or implied warranties.

All products, dates, and figures specified are preliminary based on current expectations, and are subject to change without notice.

Intel, processors, chipsets, and desktop boards may contain design defects or errors known as errata, which may cause the product to deviate from published specifications. Current characterized errata are available on request.

Intel technologies’ features and benefits depend on system configuration and may require enabled hardware, software or service activation. Performance varies depending on system configuration. No computer system can be absolutely secure. Check with your system manufacturer or retailer or learn more at https://intel.com.

Some results have been estimated or simulated using internal Intel analysis or architecture simulation or modeling, and provided to you for informational purposes. Any differences in your system hardware, software or configuration may affect your actual performance.

Intel and the Intel logo are trademarks of Intel Corporation in the United States and other countries.

*Other names and brands may be claimed as the property of others.
Copyright © Intel Corporation 2019

Report a Vulnerability

If you have information about a security issue or vulnerability with an Intel branded product or technology, please send an e-mail to secure@intel.com. Encrypt sensitive information using our PGP public key.

Please provide as much information as possible, including:

  • The products and versions affected
  • Detailed description of the vulnerability
  • Information on known exploits

A member of the Intel Product Security Team will review your e-mail and contact you to collaborate on resolving the issue. For more information on how Intel works to resolve security issues, see:

For issues related to Intel's external web presence (Intel.com and related subdomains), please contact Intel's External Security Research team.

Need product support?

The secure@intel.com e-mail address should only be used for reporting security issues.

If you...

  • Have questions about the security features of an Intel product
  • Require technical support
  • Want product updates or patches


Please visit Support & Downloads.