Open In App

Spectre Security Vulnerability

Last Updated : 11 Mar, 2024
Like Article

What is Spectre security vulnerability?

Spectre is a security vulnerability that affects all modern processors that use mechanisms such as branch prediction and speculative action. 
Spectre attacks involve inducing a victim to speculatively perform operations that would not occur during correct program execution and which leak the victim’s confidential information via a side-channel to the adversary. This also exposes otherwise protected memory space, allowing the malicious agent to access the data, or even modify it. It was discovered at the same time as Meltdown Vulnerability

What are Branch Prediction and Speculative Action mechanisms?

  • Branch Prediction: The branch prediction technique allows the processor to speed up the execution in a pipelined processor by converting instructions into predicate logic. Hence, only those instructions are executed whose predicate is true. This allows the CPU to avoid checking every single branch for execution.
  • Speculative Execution: Speculative Execution, along with branch prediction, is a component of out-of-order execution that is used for speeding up execution in pipeline-based microprocessors. We learned from the previous definition that branch prediction is used to determine which instruction will execute in case of a conditional jump. Speculative action goes one step further. It determines what the result would be from executing the next instruction(s). If the branch prediction was correct, the result is used, otherwise, it is discarded.

How does Spectre Vulnerability work?

There are two ways in which Spectre Vulnerability works: 
1. Local exploitation: 
In this case, the malicious agent lies in the computer itself. The following are the steps that occur:  

  1. It manipulates the process to execute an instruction that would never have been executed normally
  2. When the CPU evaluates the executed instruction, it throws away the computation.
  3. However, the expanded size of the cache isn’t restored.
  4. By simply looking up into the cache, the contents which were there, and their actual memory location can be deduced, thus exposing them to the malicious program

2. Remote Exploitation: 
In this case, the malicious agent works through Javascript. The scripted malware gets access to all the memory-mapped with the browser. The following steps are taken:  

  1. The cache is forced to be flushed by doing incremental reads on large datasets because array memories in javascript are maintained using the LRU policy.
  2. The branch predictor would then be mistrained by iterating over a very large dataset using bitwise operations for setting the index to in-range values, and then using an out-of-bounds address for the final iteration.
  3. By iterating over a large dataset by using bitwise operations to set in-range values, and using out of bounds addresses for the final iteration, the branch predictor can be mistrained
  4. Timed-reads enable the script to read the location

What mitigation steps are being taken?

The discovery of this security issue leads to many prevention and mitigation measures to be developed. Different processor and software vendors addressed the issue differently in the following ways:  

  1. In March 2018, Intel developed hardware fixes for Spectre. The vulnerabilities were mitigated by a new partitioning system that improves the process and privilege-level separation.
  2. Microsoft acted by isolating Kernel and user page tables. It has also designed new CPU instructions (Windows compatible) which eliminate branch speculation.
  3. Chrome 64 includes mitigation against the attack by default. Chrome 63 users can manually mitigate the attack by enabling the Site Isolation feature (chrome://flags#enable-site-per-process)
  4. Google created a new technique called ‘Retpoline’ that involves compiler-level steering of indirect branches towards a different target that does not result in a vulnerable speculative out-of-order execution taking place.
  5. Mozilla is reducing the resolution of JavaScript timers to help prevent timing attacks, with additional work on time-fuzzing techniques planned for future releases.

It is, however, to be noted that the introduction of software patches has led to significant performance issues, especially on old computers. Also, unwanted reboots have been reported even for newer Intel chips.&nbsp.

Like Article
Suggest improvement
Share your thoughts in the comments

Similar Reads