On January 27, 2020, intel released a security update that disclosed two security vulnerabilities of Intel processors that could lead to information disclosure. CVE numbers are CVE-2020-0548 and CVE-2020-0549. Intel will be providing fixes in future microcode updates. The vulnerability details are as follows:
CVE-2020-0549：L1D Eviction Sampling
On some processors under certain microarchitectural conditions, data from the most recently evicted modified L1 data cache (L1D) line may be propagated into an unused (invalid) L1D fill buffer. On processors affected by Microarchitectural Data Samping (MDS) or Transactional Asynchronous Abort (TAA), data from an L1D fill buffer may be inferred using one of these data sampling side channel methods. By combining these two behaviors together, it may be possible for a malicious actor to infer data values from modified cache lines that were previously evicted from the L1 data cache. This is called L1D eviction sampling.
Cleanup errors in some data cache evictions for some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access. This vulnerability has been assigned CVE-2020-0549 with a CVSS of 2.8.
Inspur started the relevant investigation work in the first time. Inspur will be working closely with Intel to provide security updates. Inspur PSIRT will update the security notice at any time. Please keep an eye on the security bulletin for this incident.
The affected products and corresponding update versions are shown in the table below.
|CVE||V3.1 Vector(Base)||Base Score||V3.1 Vector(Temporal Score)||Temporal Score|
|Product||BIOS Update version|
Inspur provides method to update CPU Microcode of its various products as mentioned in the table above.Download your product’s corresponding BIOS image and perform the BIOS upgrade.
Please visit the Support and Downloads site for updates on the applicable products.
20200713-V1.2-Updated The Fix Version
20200609-V1.1-Updated The Fix Version
For issues about implementing the recommendations of this Security Bulletin, contact normal Inspur Services Support channel. For other issues about the content of this Security Bulletin, send e-mail to email@example.com.
To initiate a subscription to receive future Inspur Security Bulletin via Email:Subscribe to Security Bulletins
To report a potential security vulnerability for Inspur product: Reporting a Security Vulnerability
Inspur shall not be liable for technical or editorial errors or omissions contained herein. The information provided is provided "as is" without warranty of any kind. To the extent permitted by law, Inspur disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose, title and non-infringement. In no event shall Inspur or any of its directly or indirectly controlled subsidiaries or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages. Your use of the document, by whatsoever means, will be totally at your own risk. Inspur is entitled to amend or update this document from time to time.