DOCSLIB.ORG

Instrew: Fast LLVM-Based Dynamic Binary Instrumentation and Translation

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Instrew: Fast LLVM-Based Dynamic Binary Instrumentation and Translation Instrew: Fast LLVM-based Dynamic Binary Instrumentation and Translation Alexis Engelke Martin Schulz Chair of Computer Architecture and Parallel Systems Department of Informatics Technical University of Munich LLVM Performance Workshop at CGO 2021, virtual Alexis Engelke 2021 Dynamic Binary Translation Dynamic Binary Instrumentation I Run program on other architecture, I Modify program behavior, translate code for host CPU add additional code/checks I Use-cases: compatibility, I Use-cases: analysis, debugging, architecture research profiling, arch. research I Example: QEMU-user, Rosetta 2 I Examples: Valgrind, Pin x86-64 AArch64 x86-64 x86-64 +checks mov rax, rcx mov rax, rcx mov rax, rcx add x0, x1, 4 add rax, 4 add rax, 4 add rax, 4 call check_bounds mov [rdx+rsi+16], rax add x16, x6, 16 mov [rdx+rsi+16], rax mov [rdx+rsi+16], rax str x0, [x2, x16] incq [num_stores] Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 2 Alexis Engelke 2021 Motivation: LLVM for DBT/DBI I Many DBT/DBI systems focus on translation performance I QEMU, Valgrind, Pin, . I Instead, use LLVM code generation for run-time performance Instrew: a fast LLVM-based DBT/DBI framework Step 1 Step 2 Step 3 Lift machine Align LLVM code code ! LLVM-IR gen. for DBI/DBT Performance Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 3 Alexis Engelke 2021 Overview: Process-level DBT and DBI Execution Unit Translation Instrumentation Guest Code Decode & Lift Decode & Lift main Execution Arch-indep.Arch-indep. IR IR Archdep.IR loop Manager Instrument Code Gen. Code Gen. Code Cache Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 4 Alexis Engelke 2021 Overview: Process-level DBT and DBI Execution Unit Transformation Unit Guest Code Decode & Lift main Execution Arch-indep. IR: LLVM-IR loop Manager Instrument Code Gen. Code Cache Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 5 Alexis Engelke 2021 Lifting Machine Code to LLVM-IR I Actually widely researched... I McSema: excellent coverage of x86-64 and others, but slow I HQEMU/DBILL (TCG!LLVM): limited by TCG (FP, basic blocks) I MCTOLL: very low instruction coverage I ... but not sufficient for good coverage and overall performance! Rellume: performance-oriented lifting library Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 6 Alexis Engelke 2021 Rellume: Lifting Approach I Target-independent & idiomatic LLVM-IR I Use LLVM constructs where possible, e.g. vectors, comparisons I Helper functions for syscalls and cpuid I Lifting performance: avoid heavy transformations (like mem2regs) I Lifting stages: 1. Decode instructions, recover control flow with basic blocks 2. Lift individual instructions/basic blocks 3. Fixup branches and PHI nodes I Architectures: x86-64 (up to SSE2), RISC-V64 (imafdc) Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 7 Alexis Engelke 2021 Rellume: Example define void @func_40061e(i8* %cpu) { prologue: ; ... bb_40061e: %rsp_2 = phi i64 [%rsp, %prologue] ; sub rsp, 176 Lift instruction %rsp_3 = sub i64 %rsp_2, 176 semantics ; ... compute flags ... br label %epilogue epilogue: ; ... } Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 8 Alexis Engelke 2021 Rellume: Example define void @func_40061e(i8* %cpu) { Single LLVM function, prologue: single parameter: ; ... CPU state I Instruction pointer I Registers bb_40061e: ; ... I Status flags I TLS pointer I ... epilogue: ; ... } Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 9 Alexis Engelke 2021 Rellume: Example define void @func_40061e(i8* %cpu) { prologue: %rip_p_i8 = getelementptr i8, i8* %cpu, i64 0 Construct ptrs. into CPU %rip_p = bitcast i8* %rip_p_i8 to i64* struct %rsp_p_i8 = getelementptr i8, i8* %cpu, i64 40 %rsp_p = bitcast i8* %rsp_p_i8 to i64* %rsp = load i64, i64* %rsp_p Load registers into SSA ; ... load other registers ... variables br label %bb_40061e bb_40061e: ; ... epilogue: ; ... } Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 10 Alexis Engelke 2021 Rellume: Example define void @func_40061e(i8* %cpu) { prologue: ; ... bb_40061e: ; ... epilogue: %rsp_4 = phi i64 [%rsp_3, %bb_40061e] store i64 %rsp_4, i64* %rsp_p Store new values ; ... store flags ... store i64 0x400625, i64* %rip_p Store new RIP ret void } Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 11 Alexis Engelke 2021 The good Functional! Fast! Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 12 Alexis Engelke 2021 The bad: LLVM’s limitations I Better use of host registers possible I Keep more guest registers in host registers, less memory accesses I x86-64 has (slightly broken) HHVM calling convention I Need for general all-regs CC I LLVM 11 is 40% slower than LLVM 9 I Not investigated yet Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 13 Alexis Engelke 2021 The ugly: hard problems I Floating-point semantics I Rounding mode depends on register, impossible to model in LLVM-IR I Current state: ignore rounding, except for FP!int (emulate in software) I Load-Locked/Store-Conditional atomics I Can’t be represented in general LLVM-IR I Ideas: hardware transactional memory, global mutex, stop-the-world I Memory Consistency: multi-threaded x86-64 on hsomething elsei I Two approaches: fences everywhere or hardware support I Current state: single-threaded only :) Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 14 Alexis Engelke 2021 Instrew: Client-Server Architecture Client Process Server Process Guest Code I More flexible, options: Decode I Different server main Execution Lift: Rellume machine loop Manager (Instrument) I Permanent server I Transparent caching MCJIT ELF Code Cache I ... Linker Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 15 Alexis Engelke 2021 Instrumentation I Instrumentation tool is a shared library on server-side I Loads initial library functions into client I Compile LLVM code for target architecture, send to client I Modify lifted code prior to compilation I Optionally, lifter adds instruction information to LLVM-IR I Memory management currently rather simple I 48 bytes storage accessible in CPU state I Further memory custom allocation with mmap Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 16 Alexis Engelke 2021 Evaluation I Run on SPEC CPU2017 benchmarks I Source architectures: x86-64, RISC-V64 I Target architectures: x86-64, AArch64 I LLVM 9 I Comparison with Valgrind, DynamoRIO, QEMU, HQEMU; base: host run System x86-64: 2×Intel Xeon CPU E5-2697 v3 (Haswell) @ 2.6 GHz (3.6 GHz Turbo), 17 MiB L3 cache; 64 GiB main memory; SUSE Linux 15.1 SP1; Linux kernel 4.12.14-95.32; 64-bit mode. Compiler: GCC 9.2.0 with -O3 -march=x86-64, implies SSE/SSE2 but no SSE3+/AVX. Libraries: glibc 2.32; LLVM 9.0. System AArch64: 2×Cavium ThunderX2 99xx @ 2.5 GHz, 32 MiB L3 cache; 512 GiB main memory; CentOS 8; Linux kernel 4.18.0-193.14.2; 64-bit mode. Compiler: GCC 10 with -O3. Libraries: glibc 2.32; LLVM 9.0. SPEC CPU2017 intspeed+fpspeed benchmarks, ref workload, single thread. Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 17 Alexis Engelke 2021 SPEC CPU2017int Results Results normalized to native execution on host Valgrind DynamoRIO QEMU HQEMU Instrew 6 5 4 3 2 Normalized run-time 1 0 X86toX86 RV64toX86 X86toA64 RV64toA64 Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 18 Alexis Engelke 2021 SPEC CPU2017int+fp Results (x86-64!x86-64) Native QEMU HQEMU Instrew 30 28 26 24 22 20 18 16 14 12 10 8 Normalized run-time 6 4 2 0 657.xz 602.gcc 605.mcf 619.lbm 621.wrf 644.nab geomean 625.x264 641.leela 627.cam4628.pop2 654.roms 603.bwaves 620.omnetpp 638.imagick 631.deepsjeng 649.fotonik3d 623.xalancbmk 648.exchange2 607.cactuBSSN Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 19 Alexis Engelke 2021 SPEC CPU2017int+fp Results (x86-64!x86-64) Native QEMU HQEMU Instrew 30 28 26 Instrew Best Case 24 22 Instrew: 1.07x; HQEMU: 1.17x 20 18 16 14 12 10 8 Normalized run-time 6 4 2 0 657.xz 602.gcc 605.mcf 619.lbm 621.wrf 644.nab geomean 625.x264 641.leela 627.cam4628.pop2 654.roms 603.bwaves 620.omnetpp 638.imagick 631.deepsjeng 649.fotonik3d 623.xalancbmk 648.exchange2 607.cactuBSSN Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 20 Alexis Engelke 2021 SPEC CPU2017int+fp Results (x86-64!x86-64) Native QEMU HQEMU Instrew 30 28 26 Rewriting Time Matters 24 22 Instrew: 4.2x; HQEMU: 4.0x 20 18 High rewriting time: 55% 16 14 12 10 8 Normalized run-time 6 4 2 0 657.xz 602.gcc 605.mcf 619.lbm 621.wrf 644.nab geomean 625.x264 641.leela 627.cam4628.pop2 654.roms 603.bwaves 620.omnetpp 638.imagick 631.deepsjeng 649.fotonik3d 623.xalancbmk 648.exchange2 607.cactuBSSN Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 21 Alexis Engelke 2021 Rewriting Overhead I Mean Rewriting Time: <2% I Notable exception: 602.gcc with 55% I HHVM-CC on x86 hosts: codegen.-time increase 12%–78% I Mean Rewriting Time Breakdown: I Most time spent for machine code generation I SelectionDAG instruction selector known to be slow I Replacement GlobalISel not yet ready Lift (12%) Optimize (22%) Code Gen. (65%) Link (<1%) Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 22 Alexis Engelke 2021 Instrew: LLVM-based DBI/DBT I Fast Dynamic Binary Instrumentation/Translation based on LLVM I Lift whole functions directly to LLVM-IR I Client-server approach enabling further optimizations I 50% less overhead compared to current LLVM-based DBT Instrew is Free Software! https://github.com/aengelke/instrew Introduction Machine Code ! LLVM Instrumentation Framework Performance Results 23.
Load more

Recommended publications
  • Dynamic Optimization of IA-32 Applications Under Dynamorio by Timothy Garnett
    Dynamic Optimization of IA-32 Applications Under DynamoRIO by Timothy Garnett Submitted to the Department of Electrical Engineering and Computer Science in Partial Fulfillment of the Requirements for the Degree of Master of Engineering in Computer Science Abstract The ability of compilers to optimize programs statically is diminishing. The advent and increased use of shared libraries, dynamic class loading, and runtime binding means that the compiler has, even with difficult to accurately obtain profiling data, less and less knowledge of the runtime state of the program. Dynamic optimization systems attempt to fill this gap by providing the ability to optimize the application at runtime when more of the system's state is known and very accurate profiling data can be obtained. This thesis presents two uses of the DynamoRIO runtime introspection and modification system to optimize applications at runtime. The first is a series of optimizations for interpreters running under DynamoRIO's logical program counter extension. The optimizations include extensions to DynamoRIO to allow the interpreter writer add a few annotations to the source code of his interpreter that enable large amounts of optimization. For interpreters instrumented as such, improvements in performance of 20 to 60 percent were obtained. The second use is a proof of concept for accelerating the performance of IA-32 applications running on the Itanium processor by dynamically translating hot trace paths into Itanium IA-64 assembly through DynamoRIO while allowing the less frequently executed potions of the application to run in Itanium's native IA-32 hardware emulation. This transformation yields speedups of almost 50 percent on small loop intensive benchmarks.
    [Show full text]
  • Dynamic Binary Translation & Instrumentation
    Dynamic Binary Translation & Instrumentation Pin Building Customized Program Analysis Tools with Dynamic Instrumentation CK Luk, Robert Cohn, Robert Muth, Harish Patil, Artur Klauser, Geoff Lowney, Steven Wallace, Kim Hazelwood Intel Vijay Janapa Reddi University of Colorado http://rogue.colorado.edu/Pin PLDI’05 2 Instrumentation • Insert extra code into programs to collect information about execution • Program analysis: • Code coverage, call-graph generation, memory-leak detection • Architectural study: • Processor simulation, fault injection • Existing binary-level instrumentation systems: • Static: • ATOM, EEL, Etch, Morph • Dynamic: • Dyninst, Vulcan, DTrace, Valgrind, Strata, DynamoRIO C Pin is a new dynamic binary instrumentation system PLDI’05 3 A Pintool for Tracing Memory Writes #include <iostream> #include "pin.H" executed immediately before a FILE* trace; write is executed • Same source code works on the 4 architectures VOID RecordMemWrite(VOID* ip, VOID* addr, UINT32 size) { fprintf(trace,=> “%p: Pin Wtakes %p %dcare\n”, of ip, different addr, size); addressing modes } • No need to manually save/restore application state VOID Instruction(INS ins, VOID *v) { if (INS_IsMemoryWrite(ins))=> Pin does it for you automatically and efficiently INS_InsertCall(ins, IPOINT_BEFORE, AFUNPTR(RecordMemWrite), IARG_INST_PTR, IARG_MEMORYWRITE_EA, IARG_MEMORYWRITE_SIZE, IARG_END); } int main(int argc, char * argv[]) { executed when an instruction is PIN_Init(argc, argv); dynamically compiled trace = fopen(“atrace.out”, “w”); INS_AddInstrumentFunction(Instruction,
    [Show full text]
  • Pin: Building Customized Program Analysis Tools with Dynamic Instrumentation
    Pin: Building Customized Program Analysis Tools with Dynamic Instrumentation Chi-Keung Luk Robert Cohn Robert Muth Harish Patil Artur Klauser Geoff Lowney Steven Wallace Vijay Janapa Reddi Kim Hazelwood Intel Corporation ¡ University of Colorado ¢¤£¦¥¨§ © £ ¦£ "! #%$&'( £)&(¦*+©-,.+/01$©-!2 ©-,2¦3 45£) 67©2, £¦!2 "0 Abstract 1. Introduction Robust and powerful software instrumentation tools are essential As software complexity increases, instrumentation—a technique for program analysis tasks such as profiling, performance evalu- for inserting extra code into an application to observe its behavior— ation, and bug detection. To meet this need, we have developed is becoming more important. Instrumentation can be performed at a new instrumentation system called Pin. Our goals are to pro- various stages: in the source code, at compile time, post link time, vide easy-to-use, portable, transparent, and efficient instrumenta- or at run time. Pin is a software system that performs run-time tion. Instrumentation tools (called Pintools) are written in C/C++ binary instrumentation of Linux applications. using Pin’s rich API. Pin follows the model of ATOM, allowing the The goal of Pin is to provide an instrumentation platform for tool writer to analyze an application at the instruction level with- building a wide variety of program analysis tools for multiple archi- out the need for detailed knowledge of the underlying instruction tectures. As a result, the design emphasizes ease-of-use, portabil- set. The API is designed to be architecture independent whenever ity, transparency, efficiency, and robustness. This paper describes possible, making Pintools source compatible across different archi- the design of Pin and shows how it provides these features.
    [Show full text]
  • An Infrastructure for Adaptive Dynamic Optimization
    An Infrastructure for Adaptive Dynamic Optimization Derek Bruening, Timothy Garnett, and Saman Amarasinghe Laboratory for Computer Science Massachusetts Institute of Technology Cambridge, MA 02139 fiye,timothyg,[email protected] Abstract ing profile information improves the predictions but still falls short for programs whose behavior changes dynami- Dynamic optimization is emerging as a promising ap- cally. Additionally, many software vendors are hesitant to proach to overcome many of the obstacles of traditional ship binaries that are compiled with high levels of static op- static compilation. But while there are a number of com- timization because they are hard to debug. piler infrastructures for developing static optimizations, Shifting optimizations to runtime solves these problems. there are very few for developing dynamic optimizations. Dynamic optimization allows the user to improve the per- We present a framework for implementing dynamic analy- formance of binaries without relying on how they were ses and optimizations. We provide an interface for build- compiled. Furthermore, several types of optimizations are ing external modules, or clients, for the DynamoRIO dy- best suited to a dynamic optimization framework. These in- namic code modification system. This interface abstracts clude adaptive, architecture-specific, and inter-module opti- away many low-level details of the DynamoRIO runtime mizations. system while exposing a simple and powerful, yet efficient Adaptive optimizations require instant responses to and lightweight, API. This is achieved by restricting opti- changes in program behavior. When performed statically, a mization units to linear streams of code and using adaptive single profiling run is taken to be representative of the pro- levels of detail for representing instructions.
    [Show full text]
  • Using Dynamic Binary Instrumentation for Security(And How You May Get
    King’s Research Portal Document Version Peer reviewed version Link to publication record in King's Research Portal Citation for published version (APA): Cono D'Elia, D., Coppa, E., Palmaro, F., & Cavallaro, L. (Accepted/In press). SoK: Using Dynamic Binary Instrumentation for Security (And How You May Get Caught Red Handed). In ACM Asia Conference on Information, Computer and Communications Security (ASIACCS 2019) Citing this paper Please note that where the full-text provided on King's Research Portal is the Author Accepted Manuscript or Post-Print version this may differ from the final Published version. If citing, it is advised that you check and use the publisher's definitive version for pagination, volume/issue, and date of publication details. And where the final published version is provided on the Research Portal, if citing you are again advised to check the publisher's website for any subsequent corrections. General rights Copyright and moral rights for the publications made accessible in the Research Portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognize and abide by the legal requirements associated with these rights. •Users may download and print one copy of any publication from the Research Portal for the purpose of private study or research. •You may not further distribute the material or use it for any profit-making activity or commercial gain •You may freely distribute the URL identifying the publication in the Research Portal Take down policy If you believe that this document breaches copyright please contact [email protected] providing details, and we will remove access to the work immediately and investigate your claim.
    [Show full text]
  • Coverage-Guided Fuzzing of Grpc Interface
    Niko Lappalainen COVERAGE-GUIDED FUZZING OF GRPC INTERFACE Master of Science Thesis Faculty of Information Technology and Communication Sciences Examiners: Marko Helenius Billy Brumley January 2021 i ABSTRACT Niko Lappalainen: Coverage-guided fuzzing of gRPC interface Master of Science Thesis Tampere University Master’s Degree Programme in Information Technology January 2021 Fuzz testing has emerged as a cost-effective method of finding security issues in many real- world targets. The software company M-Files Inc. wanted to incorporate fuzz testing to harden the security of their product M-Files Server. The newly implemented gRPC API was set as the target interface to be fuzzed. This thesis was requested to find a suitable fuzzing tool, and to verify that the tool could find and report issues. Another objective of this thesis was to determine a criterion for stopping fuzzing when adequate testing coverage has been achieved without having to run the fuzzer perpetually. To select a suitable fuzzing tool, some requirements had to be defined. Requirements and selection criteria were set based on the properties of the M-Files system as well as the target interface. Next, various fuzzing tool options were gathered from different sources. These options were validated based on the set requirements to select a short list of tools that could be analysed more closely. The suitable tool was selected from these based on their ease of integration and suspected performance. The coverage-guided WinAFL was evaluated as the most suitable from the considered options. The selected fuzzing tool was used to test M-Files Server in order to record its results.
    [Show full text]
  • Valgrind a Framework for Heavyweight Dynamic Binary
    VValgrindalgrind AA FramFrameweworkork forfor HHeavyweavyweighteight DDynamynamicic BBinaryinary InstrumInstrumentationentation Nicholas Nethercote — National ICT Australia Julian Seward — OpenWorks LLP 1 FAFAQQ #1#1 • How do you pronounce “Valgrind”? • “Val-grinned”, not “Val-grined” • Don’t feel bad: almost everyone gets it wrong at first 2 DDBBAA toolstools • Program analysis tools are useful – Bug detectors – Profilers – Visualizers • Dynamic binary analysis (DBA) tools – Analyse a program’s machine code at run-time – Augment original code with analysis code 3 BBuildinguilding DDBBAA toolstools • Dynamic binary instrumentation (DBI) – Add analysis code to the original machine code at run-time – No preparation, 100% coverage • DBI frameworks – Pin, DynamoRIO, Valgrind, etc. Tool Framework + = Tool plug-in 4 PriorPrior wworkork Well-studied Not well-studied Framework performance Instrumentation capabilities Simple tools Complex tools • Potential of DBI has not been fully exploited – Tools get less attention than frameworks – Complex tools are more interesting than simple tools 5 ShadowShadow valuevalue toolstools 6 ShadowShadow valuevalue toolstools (I)(I) • Shadow every value with another value that describes it – Tool stores and propagates shadow values in parallel Tool(s) Shadow values help find... Memcheck Uses of undefined values bugs Annelid Array bounds violations Hobbes Run-time type errors TaintCheck, LIFT, TaintTrace Uses of untrusted values security “Secret tracker” Leaked secrets DynCompB Invariants properties Redux Dynamic
    [Show full text]
  • Using Dynamic Binary Instrumentation for Security (And How You May Get Caught Red Handed)
    SoK: Using Dynamic Binary Instrumentation for Security (And How You May Get Caught Red Handed) Daniele Cono D’Elia Emilio Coppa Simone Nicchi Sapienza University of Rome Sapienza University of Rome Sapienza University of Rome [email protected] [email protected] [email protected] Federico Palmaro Lorenzo Cavallaro Prisma King’s College London [email protected] [email protected] ABSTRACT 1 INTRODUCTION Dynamic binary instrumentation (DBI) techniques allow for moni- Even before the size and complexity of computer software reached toring and possibly altering the execution of a running program up the levels that recent years have witnessed, developing reliable and to the instruction level granularity. The ease of use and flexibility of efficient ways to monitor the behavior of code under execution DBI primitives has made them popular in a large body of research in has been a major concern for the scientific community. Execution different domains, including software security. Lately, the suitabil- monitoring can serve a great deal of purposes: to name but a few, ity of DBI for security has been questioned in light of transparency consider performance analysis and optimization, vulnerability iden- concerns from artifacts that popular frameworks introduce in the tification, as well as the detection of suspicious actions, execution execution: while they do not perturb benign programs, a dedicated patterns, or data flows in a program. adversary may detect their presence and defeat the analysis. To accomplish this task users can typically resort to instrumen- The contributions we provide are two-fold. We first present the tation techniques, which in their simplest form consist in adding abstraction and inner workings of DBI frameworks, how DBI as- instructions to the code sections of the program under observation.
    [Show full text]
  • Dynamic Data Flow Analysis Via Virtual Code Integration (Aka the Spiderpig Case)
    Dynamic Data Flow Analysis via Virtual Code Integration (aka The SpiderPig case) Piotr Bania [email protected] November 2008 "I'm all alone I smoke my friends down to the lter But I feel much cleaner After it rains" - Tom Waits, Little Drop Of Poison Abstract This paper addresses the process of dynamic data ow analysis using vir- tual code integration (VCI), often refered to as dynamic binary rewriting. This article will try to demonstrate all of the techniques that were applied in the SpiderPig project [15]. It will also discuss the main dierences between the methods that were employed and those used in other available software, arXiv:0906.0724v1 [cs.CR] 3 Jun 2009 as well as introducing other related work. SpiderPig's approach was found to be very fast and was transparent enough for reliable and usable data ow analysis. It was created with the purpose of providing a tool which would aid vulnerability and security researchers with tracing and analyzing any necessary data and its further propagation through a program. At the time of writing this article, it is the authors opinion that SpiderPig oers one of the most advanced solutions for data 1 ow monitoring. At the current state it works on IA-32 platforms with Mi- crosoft Windows systems and it supports FPU, SSE1, MMX and all of the IA-32 general instructions. Furthermore it can be extended to cover other operating systems and architectures as well. SpiderPig also demonstrates the usage of a virtual code integration (VCI) framework which allows for modify- ing the target application code at the instruction level.
    [Show full text]
  • Introspective Intrusion Detection
    UNIVERSITY OF CALIFORNIA, IRVINE Introspective Intrusion Detection DISSERTATION submitted in partial satisfaction of the requirements for the degree of DOCTOR OF PHILOSOPHY in Computer Engineering by Byron Hawkins Dissertation Committee: Associate Professor Brian Demsky, Chair Professor Michael Franz Associate Professor Athina Markopoulou 2017 Portions of Chapters 1, 2, 5 c 2017 IEEE Portions of Chapters 1, 2, 3 c 2016 ACM Portions of Chapters 1, 4 c 2015 IEEE All other materials c 2017 Byron Hawkins DEDICATION To the International Justice Mission for their enduring effort to protect powerless individuals from the malicious intrusions of the real world. ii TABLE OF CONTENTS Page LIST OF FIGURES vii LIST OF TABLES ix LIST OF ALGORITHMS x ACKNOWLEDGMENTS xi CURRICULUM VITAE xii ABSTRACT OF THE DISSERTATION xiv 1 Introduction 1 1.1 Timeline of Important RCE Defenses . 8 1.1.1 Bug Fixing . 9 1.1.2 Traditional Intrusion Detection . 10 1.1.3 Control Flow Integrity . 12 1.1.4 Diversification . 14 1.2 Theoretical Advantages and Challenges of IID . 16 1.3 Goals of Introspective Intrusion Detection . 24 1.4 Usage Model . 29 1.4.1 Forensics . 30 1.4.2 Advanced Persistent Threats . 32 1.4.3 Field Debugging . 35 1.4.4 Profiling . 37 1.5 Prototype IID Implementations . 38 1.5.1 BlackBox for x86 COTS Binaries . 40 1.5.2 ZenIDS for PHP Applications . 42 1.6 Contributions . 44 1.7 Organization . 45 2 Paradise: a Hypothetically Pure IID 46 2.1 Platform Snares . 47 2.2 Generic Threat Model . 51 2.3 Deployment . 52 2.3.1 Generating the Trusted Profile .
    [Show full text]
  • A Platform for Secure Static Binary Instrumentation ∗
    A Platform for Secure Static Binary Instrumentation ∗ Mingwei Zhang Rui Qiao Niranjan Hasabnis R. Sekar Stony Brook University Abstract instrumentations can be more easily and extensively opti- Program instrumentation techniques form the basis of many mized by exploiting higher level information such as types. recent software security defenses, including defenses against However, binary instrumentations are more widely applica- common exploits and security policy enforcement. As com- ble since users have ready access to binaries. Moreover, se- pared to source-code instrumentation, binary instrumenta- curity instrumentations should be applied to all code, includ- tion is easier to use and more broadly applicable due to the ing all libraries, inline assembly code, and any code inserted ready availability of binary code. Two key features needed by the compiler/linker. Here again, binary based techniques for security instrumentations are (a) it should be applied are advantageous. to all application code, including code contained in various Binary instrumentation can either be static or dynamic. system and application libraries, and (b) it should be non- Static binary instrumentation (SBI) is performed offline on bypassable. So far, dynamic binary instrumentation (DBI) binary files, whereas dynamic binary instrumentation (DBI) techniques have provided these features, whereas static bi- operates on code already loaded into main memory. DBI nary instrumentation (SBI) techniques have lacked them. techniques disassemble and instrument each basic block just These features, combined with ease of use, have made DBI before its first execution. DBI has been the technique of the de facto choice for security instrumentations. However, choice for security instrumentation of COTS binaries. Pre- DBI techniques can incur high overheads in several common vious works have used DBI for sandboxing [15, 17], taint- usage scenarios, such as application startups, system-calls, tracking [23, 28], defense from return-oriented program- and many real-world applications.
    [Show full text]
  • Transparent Dynamic Instrumentation
    Transparent Dynamic Instrumentation Derek Bruening Qin Zhao Saman Amarasinghe Google, Inc. Google, Inc Massachusetts Institute of Technology [email protected] [email protected] [email protected] Abstract can be executed, monitored, and controlled. A software code cache Process virtualization provides a virtual execution environment is used to implement the virtual environment. The provided layer within which an unmodified application can be monitored and con- of control can be used for various purposes including security en- trolled while it executes. The provided layer of control can be used forcement [14, 22], software debugging [8, 43], dynamic analy- for purposes ranging from sandboxing to compatibility to profil- sis [42, 45], and many others [40, 41, 44]. The additional operations ing. The additional operations required for this layer are performed are performed clandestinely alongside regular program execution. clandestinely alongside regular program execution. Software dy- First presented in 2001 [9], DynamoRIO evolved from a re- namic instrumentation is one method for implementing process search project [6, 10] for dynamic optimization to the flagship virtualization which dynamically instruments an application such product of a security company [22] and finally an open source that the application’s code and the inserted code are interleaved to- project [1]. Presently it is being used to build tools like Dr. Mem- gether. ory [8] that run large applications including proprietary software on DynamoRIO is a process virtualization system implemented us- both Linux and Windows. There are many challenges to building ing software code cache techniques that allows users to build cus- such a system that supports executing arbitrary unmodified appli- tomized dynamic instrumentation tools.
    [Show full text]