Context-Sensitive Fencing: Securing Speculative Execution Via

Context-Sensitive Fencing: Securing Speculative Execution Via

Context-Sensitive Fencing: Securing Speculative Execution via Microcode Customization Mohammadkazem Taram Ashish Venkat Dean Tullsen University of California San Diego University of Virginia University of California San Diego [email protected] [email protected] [email protected] Abstract processor architectures feature highly complex and sophis- This paper describes context-sensitive fencing (CSF), a micro- ticated performance optimizations. However, scaling per- code-level defense against multiple variants of Spectre. CSF formance without considering security implications could leverages the ability to dynamically alter the decoding of have serious negative consequences, as evidenced by the the instruction stream, to seamlessly inject new micro-ops, recent pile of lawsuits [96] concerning the Meltdown [61] including fences, only when dynamic conditions indicate and Spectre [57] class of microarchitectural attacks. These they are needed. This enables the processor to protect against events have highlighted the need to architect systems that the attack, but with minimal impact on the efficacy of key can not only run at high speed, but can also exhibit high performance features such as speculative execution. resilience against security attacks, not just one or the other. This research also examines several alternative fence im- The goal of this work is to secure a particular performance plementations, and introduces three new types of fences optimization integral to modern processor architectures – which allow most dynamic reorderings of loads and stores, speculative execution – against the Spectre class of microar- but in a way that prevents speculative accesses from chang- chitectural attacks, while maintaining acceptably high levels ing visible cache state. These optimizations reduce the per- of performance. formance overhead of the defense mechanism, compared Modern processors employ branch speculation and out-of- to state-of-the-art software-based fencing mechanisms by a order execution to take advantage of the available instruction- factor of six. level parallelism beyond control-flow boundaries, thereby improving the overall CPU resource utilization and sustain- CCS Concepts • Security and privacy → Side-channel ing high throughput. Spectre attacks exploit speculative ex- analysis and countermeasures; Systems security; Informa- ecution by leaking secret information along misspeculated tion flow control; • Computer systems organization → paths via cache-based and other timing side channels. Owing Architectures. to their ability to mistrain the branch predictor to deliber- Keywords secure architectures; side-channel attacks; Spec- ately steer execution to an attacker-intended control-flow tre; speculative execution; microcode; taint tracking path [49, 58], these attacks have notably demonstrated the potential to break all confidentiality and completely bypass ACM Reference Format: important hardware/software security mechanisms such as Mohammadkazem Taram, Ashish Venkat, and Dean Tullsen. 2019. ASLR, even via remotely accessed covert channels [76]. Context-Sensitive Fencing: Securing Speculative Execution via Mi- Mitigating Spectre is a particularly hard problem since crocode Customization. In Proceedings of 2019 Architectural Support for Programming Languages and Operating Systems (ASPLOS’19). it could potentially cause highly intrusive changes to the ACM, New York, NY, USA, 16 pages. https://doi.org/10.1145/3297858. existing out-of-order processor design, severely limiting per- 3304060 formance. Although Intel has announced microcode update patches to mitigate certain variants of the attack, a major- 1 Introduction ity of the high impact vulnerabilities still largely rely on Maximizing performance has been a major driving force software patching [45, 72]. State-of-the-art software counter- in the economics of the microprocessor industry. Modern measures take advantage of fences that mute specific effects of speculative execution by constraining the order of certain Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not memory operations, or in some cases by completely serial- made or distributed for profit or commercial advantage and that copies bear izing a portion of the dynamic instruction stream. Liberal this notice and the full citation on the first page. Copyrights for components fence insertion (e.g., at every bounds check) can mitigate the of this work owned by others than ACM must be honored. Abstracting with attacks, but doing so severely hurts performance; however, credit is permitted. To copy otherwise, or republish, to post on servers or to spraying fences more strategically at appropriate locations redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]. in the code requires extensive patching of software via re- ASPLOS’19, April 13–17, 2019, Providence, RI, USA compilation or binary translation – resulting in significant © 2019 Association for Computing Machinery. engineering effort and long delays to deployment. We need ACM ISBN ISBN 978-1-4503-6240-5/19/04...$15.00 https://doi.org/10.1145/3297858.3304060 hardware architectures that can more seamlessly react to • It introduces context-sensitive fencing, a mechanism such attacks via unobtrusive field updates. that leverages a dynamic decoding architecture to in- This work proposes context-sensitive fencing (CSF), a novel ject fences between control flow and loads, without microcode-level defense against Spectre. The key compo- recompilation or binary translation. nents of the defense strategy include: (a) a microcode cus- • It examines several variants of existing fences, and tomization mechanism that allows processors to surgically introduces three new fences, which allow aggressive insert fences into the dynamic instruction stream to miti- reordering of loads and stores without exposing any gate undesirable side-effects of speculative execution, (b) a microarchitectural evidence, in the cache, of specula- decoder-level information flow tracking (DLIFT) framework tive accesses that cross the fence. that identifies potentially unsafe execution patterns to trig- • It introduces a decoder-level dynamic information ger microcode customization, and (c) mistraining mitigations flow tracker, DLIFT, which allows accurate tracking that secure the branch predictor and the return address stack. of taints early in the pipeline, giving the pipeline the To perform secure microcode customization with mini- ability to identify tainted accesses before the stages mal impact on performance, this work leverages context- that enable speculative execution. sensitive decoding (CSD) [80], a recently proposed extension • It introduces a simple dynamic mechanism that elimi- to Intel’s (and others’) micro-op translation mechanism that nates redundant (per basic block) fences. enables on-demand and context-sensitive customization of • The combination of optimizations introduced in this the dynamic micro-op instruction stream. In addition, this paper reduce the cost of a fence-based Spectre mitiga- work also takes advantage of the reconfiguration framework tion technique from 48% overhead (for a conservative offered by CSD, allowing the operating system and other scheme) to less than 8%. trusted entities to dynamically control the frequency, type, • It also introduces a decode-level branch predictor iso- and behavior of fences that are surgically inserted into the lation technique that mitigates branch mis-training micro-op stream to secure speculative execution. variants of Spectre. This work analyzes a significantly expanded suite of fences, considering different possible enforcement stages and en- forcement strategies. In particular, we introduce a new fence 2 Background and Related Work that prevents speculative updates to cache state with mini- Speculative Execution. Dynamic control speculation is a mal interference in the dynamic scheduling of instructions. well-known instruction throughput optimization technique Context-sensitive fencing has the ability to automatically used, especially in out-of-order processors, to predict the identify fence insertion points via a novel decoder-level infor- branch outcome and execute instructions along the predicted mation flow tracking-based detection mechanism. Since the path, while waiting for the actual branch outcome to be eval- processor front-end typically churns instructions at a much uated at a later pipeline stage. In the event of a mispredic- higher rate than the rest of the pipeline, information-flow tion, the processor rolls back execution along the misspec- tracking at the decoder-level is prone to frequent overtaint- ulated path and redirects control to the right branch tar- ing and undertainting scenarios. While overtainting could get. Although speculative execution is largely programmer- hurt performance due to the increased frequency of fence invisible in terms of committed architectural register and insertion, undertainting could undermine the security of memory state, in all known instances it leaves some mi- the system for a brief window. By solving these challenges croarchitectural side effects that can be observed through through an early and low-overhead mistaint detection and well-established side channels. recovery mechanism, this paper further establishes the viabil- Microarchitectural Attacks. Microarchitectural attacks ity of decoder-level information

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    16 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us