Get 20M+ Full-Text Papers For Less Than $1.50/day. Start a 14-Day Trial for You or Your Team.

Learn More →

Building Secure Defenses Against Code-Reuse AttacksBuilding Control-Flow Integrity Defenses

Building Secure Defenses Against Code-Reuse Attacks: Building Control-Flow Integrity Defenses [In particular, Abadi et al. [2, 4] suggest a label-based CFI approach, where each CFG node is marked with a unique label ID that is placed at the beginning of a BBL. In order to preserve the program’s original semantics, the label is either encoded as an offset into a x86 cache prefetch instruction or as simple data word. Inserting labels into a program binary will require moving instructions from their original position. As a consequence, CFI requires adjusting all memory offsets embedded into jump/call and data load/store instructions that are affected by the insertion of the additional prefetch instructions.] http://www.deepdyve.com/assets/images/DeepDyve-Logo-lg.png

Building Secure Defenses Against Code-Reuse AttacksBuilding Control-Flow Integrity Defenses

Download PDF
27 pages

Loading next page...
 
/lp/springer-journals/building-secure-defenses-against-code-reuse-attacks-building-control-o77CyMuKsF
Publisher
Springer International Publishing
Copyright
© The Author(s) 2015
ISBN
978-3-319-25544-6
Pages
27 –54
DOI
10.1007/978-3-319-25546-0_3
Publisher site
See Chapter on Publisher Site

Abstract

[In particular, Abadi et al. [2, 4] suggest a label-based CFI approach, where each CFG node is marked with a unique label ID that is placed at the beginning of a BBL. In order to preserve the program’s original semantics, the label is either encoded as an offset into a x86 cache prefetch instruction or as simple data word. Inserting labels into a program binary will require moving instructions from their original position. As a consequence, CFI requires adjusting all memory offsets embedded into jump/call and data load/store instructions that are affected by the insertion of the additional prefetch instructions.]

Published: Dec 8, 2015

Keywords: Program Execution; Return Address; Return Instruction; Performance Overhead; Target Address

There are no references for this article.