Foreshadow

Two groups of researchers discovered the security vulnerabilities independently: a Belgian team (including Raoul Strackx, Jo Van Bulck, Frank Piessens) from imec-DistriNet, KU Leuven reported it to Intel on 3 January 2018; a second team from Technion – Israel Institute of Technology (Marina Minkin, Mark Silberstein), University of Adelaide (Yuval Yarom), and University of Michigan (Ofir Weisse, Daniel Genkin, Baris Kasikci, Thomas F. Wenisch) reported it on 23 January 2018. The vulnerabilities were first disclosed to the public on 14 August 2018. ==Mechanism==

The Foreshadow vulnerability is a speculative execution attack on Intel processors that may result in the disclosure of sensitive information stored in personal computers and third-party clouds. There are two versions: the first version (original/Foreshadow) ( [attacks SGX]) targets data from SGX enclaves; and the second version (next-generation/Foreshadow-NG) ( [attacks the OS Kernel and SMM mode] and [attacks virtual machines]) targets virtual machines (VMs), hypervisors (VMM), operating systems (OS) kernel memory, and System Management Mode (SMM) memory. Intel considers the entire class of speculative execution side channel vulnerabilities as "L1 Terminal Fault" (L1TF). For Foreshadow, the sensitive data of interest is the encrypted data in an SGX enclave. Usually, an attempt to read enclave memory from outside the enclave is made, speculative execution is permitted to modify the cache based on the data that was read, and then the processor is allowed to block the speculation when it detects that the protected-enclave memory is involved and reading is not permitted. Speculative execution can use sensitive data in a level 1 cache before the processor notices a lack of permission. The Foreshadow attacks are stealthy, and leave few traces of the attack event afterwards in a computer's logs. On 16 August 2018, researchers presented technical details of the Foreshadow security vulnerabilities in a seminar, and publication, at a USENIX security conference. ==Impact==

Foreshadow is similar to the Spectre security vulnerabilities discovered earlier to affect Intel and AMD chips, and the Meltdown vulnerability that affected Intel. AMD products, according to AMD, are not affected by the Foreshadow security flaws. According to one expert, "[Foreshadow] lets malicious software break into secure areas that even the Spectre and Meltdown flaws couldn't crack". Nonetheless, one of the variants of Foreshadow goes beyond Intel chips with SGX technology, and affects "all [Intel] Core processors built over the last seven years". Intel notes that the Foreshadow flaws could produce the following: • Malicious applications, which may be able to infer data in the operating system memory, or data from other applications. • A malicious guest virtual machine (VM) may infer data in the VM's memory, or data in the memory of other guest VMs. • Malicious software running outside of SMM may infer data in SMM memory. • Malicious software running outside of an Intel SGX enclave or within an enclave may infer data from within another Intel SGX enclave. According to one of the discoverers of the computer flaws: "... the SGX security hole can lead to a "Complete collapse of the SGX ecosystem." A partial listing of affected Intel hardware has been posted, and is described below. (Note: a more detailed - and updated - listing of affected products is on the official Intel website.) • Intel Core i3/i5/i7/M processor (45 nm and 32 nm) • 2nd/3rd/4th/5th/6th/7th/8th generation Intel Core processors • Intel Core X-series processor family for Intel X99 and X299 platforms • Intel Xeon processor 3400/3600/5500/5600/6500/7500 series • Intel Xeon Processor E3 v1/v2/v3/v4/v5/v6 family • Intel Xeon Processor E5 v1/v2/v3/v4 family • Intel Xeon Processor E7 v1/v2/v3/v4 family • Intel Xeon Processor Scalable family • Intel Xeon Processor D (1500, 2100) Foreshadow may be very difficult to exploit, and there seems to be no evidence to date (15 August 2018) of any serious hacking involving the Foreshadow vulnerabilities. ==Mitigation==

Applying software patches may help alleviate some concern(s), although the balance between security and performance may be a worthy consideration. Companies performing cloud computing may see a significant decrease in their overall computing power; people should not likely see any performance impact, according to researchers. as well as new client processors expected to launch later this year [2018]." ==See also==