Lucene search

K
intelIntel Security CenterINTEL:INTEL-SA-00381
HistoryFeb 16, 2021 - 12:00 a.m.

2020.2 IPU - Intel® Processor Advisory

2021-02-1600:00:00
Intel Security Center
www.intel.com
17

Summary:

Potential security vulnerabilities in some Intel® Processors may allow information disclosure.** **Intel is releasing firmware updates to mitigate these potential vulnerabilities.

Vulnerability Details:

CVEID: CVE-2020-8698

Description: Improper isolation of shared resources in some Intel® Processors may allow an authenticated user to potentially enable information disclosure via local access.

CVSS Base Score: 5.5 Medium

CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CVEID: CVE-2020-8696

Description: Improper removal of sensitive information before storage or transfer in some Intel® Processors may allow an authenticated user to potentially enable information disclosure via local access.

CVSS Base Score: 2.5 Low

CVSS Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N

Affected Products:

A list of impacted products can be found here.

Recommendations:

Intel recommends that users of affected Intel® Processors update to the latest version firmware provided by the system manufacturer that addresses these issues.

Intel has released microcode updates for the affected Intel® Processors that are currently supported on the public github repository.

On January 25, 2021 Intel has released new microcode updates to mitigate CVE-2020-8696 for Skylake server (50654) and Cascade Lake Server (50656 & 50657) processors. The new microcode update mitigates an issue when using an active JTAG agent like In Target Probe (ITP), Direct Connect Interface (DCI) or a Baseboard Management Controller (BMC) to take the CPU JTAG/TAP out of reset and then returning it to reset.

  • Skylake Server 02006a0a
  • Cascade Lake Server B-0 04003006
  • Cascade Lake Server B-1 05003006

Please see details below on access to the microcode:

GitHub*: Public Github: <https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files&gt;

To address this issue, an SGX TCB recovery will be required in Q4 2020. Refer to Intel® SGX Attestation Technical Details for more information on the SGX TCB recovery process.

Acknowledgements:

The following issues were found internally by Intel employees. Intel would like to thank Ezra Caltum, Joseph Nuzman, Nir Shildan and Ofir Joseff.

Intel, and nearly the entire technology industry, follows a disclosure practice called Coordinated Disclosure, under which a cybersecurity vulnerability is generally publicly disclosed only after mitigations are available.