+ All Categories
Home > Documents > The Deconstruction of Dyninst : Experiences and Future Directions

The Deconstruction of Dyninst : Experiences and Future Directions

Date post: 24-Feb-2016
Category:
Upload: summer
View: 58 times
Download: 0 times
Share this document with a friend
Description:
The Deconstruction of Dyninst : Experiences and Future Directions. Drew Bernat , Madhavi Krishnan, Bill Williams, Bart Miller Paradyn Project. Why components?. Share tools Build new tools quickly. Share Tools. Paraver. 3. Dyninst Components. DyninstAPI. ProcControl API. - PowerPoint PPT Presentation
Popular Tags:
50
The Deconstruction of Dyninst: Experiences and Future Directions Drew Bernat, Madhavi Krishnan, Bill Williams, Bart Miller Paradyn Project 1
Transcript
Page 1: The Deconstruction of  Dyninst : Experiences  and Future Directions

The Deconstruction of Dyninst:Experiences and Future

DirectionsDrew Bernat, Madhavi

Krishnan, Bill Williams, Bart Miller

Paradyn Project

1

Page 2: The Deconstruction of  Dyninst : Experiences  and Future Directions

Why components?

Share toolsBuild new tools quickly

2

Page 3: The Deconstruction of  Dyninst : Experiences  and Future Directions

Share Tools

33

Paraver

Page 4: The Deconstruction of  Dyninst : Experiences  and Future Directions

DataflowAPI

Dyninst Components

4

PatchAPI

InstructionAPI

ParseAPI

StackwalkerAPI

ProcControlAPI

CodeGenAPI

SymtabAPI

DynCAPI

DyninstAPI

Page 5: The Deconstruction of  Dyninst : Experiences  and Future Directions

StackwalkerAPI A Dyninst Component

Dyninst Component Users

5

SymtabAPI A Dyninst Component

Page 6: The Deconstruction of  Dyninst : Experiences  and Future Directions

Build New Tools Quickly: Dataflow Analysis

6

compiler• PowerPC jump tables and return instruction

detection• Malware return address tampering• Behavior-preserving relocation

Page 7: The Deconstruction of  Dyninst : Experiences  and Future Directions

Build New Tools Quickly: Binary Rewriter

7

SymtabAPI A Dyninst Component

Page 8: The Deconstruction of  Dyninst : Experiences  and Future Directions

Build New Tools Quickly: Unstrip

8

011000101…110101101…011101…1101110101

targ8056f50 targ805c3bd0

targ805ee40targ8057220

ParseAPI A Dyninst Component

SymtabAPI

A Dyninst Component

getpidkill

compiler

Symbol Table

Data

Page 9: The Deconstruction of  Dyninst : Experiences  and Future Directions

July 2007

Down The Memory LaneSymtabAPI – version 1.0DynStackwalker – coming soonInstructionAPI – proposedBinInst – proposed

9

Page 10: The Deconstruction of  Dyninst : Experiences  and Future Directions

PatchAPI A Dyninst Component ParseAPI

A Dyninst Component DataflowAPI

A Dyninst Component

DynC API A Dyninst

Component

SymtabAPI A Dyninst Component

StackwalkerAPI

A Dyninst Component

InstructionA

PI A Dyninst

Component

ProcControlAPI A Dyninst Component

Dyninst Components Timeline

10

2006 2007 2008 2009 2010 2011

Design and ImplementationBeta ReleaseFirst ReleaseIntegration into Dyninst

SymtabAPI

StackwalkerAPI

InstructionAPI

ParseAPI

PatchAPI

ProcControlAPI

DataflowAPI

DynCAPI

Page 11: The Deconstruction of  Dyninst : Experiences  and Future Directions

Componentization: Design DecisionsDefine the scope of the component

11

Block Edge

Function

Cached register

liveness info

Instrumentability

InstPoints

Dyninst CFG modelParseAPI CFG model

Page 12: The Deconstruction of  Dyninst : Experiences  and Future Directions

Componentization: Design DecisionsBalance internal and external user requirement

12

StackwalkerAPI A Dyninst Component

Page 13: The Deconstruction of  Dyninst : Experiences  and Future Directions

Componentization: Design DecisionsRefine requirements

13

PatchAPI A Dyninst Component

Page 14: The Deconstruction of  Dyninst : Experiences  and Future Directions

Componentization: Design DecisionsCreate right level of abstractions

14

libelfSymtabAPI A Dyninst Component

libbfd

Page 15: The Deconstruction of  Dyninst : Experiences  and Future Directions

Componentization: Design DecisionsDesign extensible and adaptable interfaces

15

StackwalkerAPI A Dyninst Component

PatchAPI A Dyninst Component

Stack frame stepper• Standard

frame• Debug frame• Signal frameParseAPI

A Dyninst Component

Page 16: The Deconstruction of  Dyninst : Experiences  and Future Directions

Componentization: Design DecisionsPlan for reintegration

16

StackwalkerAPI A Dyninst Component

ProcControlAPI A Dyninst Component

Page 17: The Deconstruction of  Dyninst : Experiences  and Future Directions

Ongoing Research

17

Page 18: The Deconstruction of  Dyninst : Experiences  and Future Directions

Ongoing Research• Lightweight, Self-Propelled Instrumentation

• Wenbin Fang• Binary Editing

• Andrew Bernat• Malware Analysis and Instrumentation

• Kevin Roundy• Binary Provenance and Authorship

• Nate Rosenblum• Instrumenting Virtualized Environments

• Emily Jacobson

18

Page 19: The Deconstruction of  Dyninst : Experiences  and Future Directions

Lightweight Instrumentation• Analyze intermittent bugs and fine-

grained performance problems • Autonomy• Little perturbation• High level of detail

• Rapid activation• Ability to analyze black-box systems

• User level and kernel level

19

Page 20: The Deconstruction of  Dyninst : Experiences  and Future Directions

User Mutator

Self-Propelled Instrumentation

20

Snippet

Snippet

PatchAPI A Dyninst Component

Page 21: The Deconstruction of  Dyninst : Experiences  and Future Directions

21

void foo() {{ bar()}

void bar(){ baz()}

How it Works

Instrumenter.so

Process

Snippet

Snippet

PatchAPI A Dyninst

Component

ProcControlAPI

A Dyninst Component

Page 22: The Deconstruction of  Dyninst : Experiences  and Future Directions

22

Binary Instrumentation

PatchAPI A Dyninst Component

ParseAPI A Dyninst Component

Page 23: The Deconstruction of  Dyninst : Experiences  and Future Directions

Binary Editing

23

Insert error checking and

handling

Predicate switching

Dynamic patching

Code surgery

Page 24: The Deconstruction of  Dyninst : Experiences  and Future Directions

Malware Analysis and Instrumentation

24

UnpackingCode

OverwritingCode

Self-Checksummin

g

Address Space

Sensitive

Page 25: The Deconstruction of  Dyninst : Experiences  and Future Directions

SR-Dyninst

25

ParseAPI A Dyninst Component

PatchAPI A Dyninst Component

ProcControlAPI

A Dyninst Component

DataflowAPI A Dyninst

Component

Parse Reachable

CodeCatch

ExceptionsDynamic

Code Discovery

Overcome Sensitivity

Page 26: The Deconstruction of  Dyninst : Experiences  and Future Directions

CFG of Conficker A

26

Page 27: The Deconstruction of  Dyninst : Experiences  and Future Directions

010111010110...

IC++

Binary Provenance and Authorship

Page 28: The Deconstruction of  Dyninst : Experiences  and Future Directions

Provenance System Overview

29

0111010110101010101011101010010110101110101101010101010111010100101101

01110101101010101010111010100101101

01110101101010101010111010100101101

TRAINING DATA BINARY ANALYSIS TOOL

ParseAPI A Dyninst

Component

LEARNING FRAMEWORK

provenance model

0111010110101010101110101110101001101101

PROGRAM

Page 29: The Deconstruction of  Dyninst : Experiences  and Future Directions

30

Language.999

Compiler.998

Optimization.993

LO HI

Version .910

175 programs x 2,686 binaries 955k functions

Acc.

Provenance Evaluation

Page 30: The Deconstruction of  Dyninst : Experiences  and Future Directions

Instrumenting Virtualized Environments

31

Page 31: The Deconstruction of  Dyninst : Experiences  and Future Directions

Status Update

32

Page 32: The Deconstruction of  Dyninst : Experiences  and Future Directions

33

Dyninst 7.0.1Major new features:o New platforms for binary rewriter

o x86 and x86_64 - statically linked binarieso ppc32 and BlueGene/P - dynamically linked

binaries o Improvements to parsing speedo Reductions in memory usage

o Deprecated Solaris and IA64 platformso AIX pending due to support difficulties

Page 33: The Deconstruction of  Dyninst : Experiences  and Future Directions

Component Status Update• SymtabAPI 7.0.1

• Speed and space optimizations• InstructionAPI 7.0.1

• PowerPC (ppc32, ppc64) platform• Full integration with Dyninst

• ParseAPI 7.0.1 - Platform independent API for parsing binaries• Control flow graph representation• Interprocedural edges (call and return)• Built on InstructionAPI and SymtabAPI• Full integration with Dyninst

34

Page 34: The Deconstruction of  Dyninst : Experiences  and Future Directions

Component Status Update• StackwalkerAPI 2.1

• Significant reduction in memory usage• ProcControlAPI 1.0.1 - Platform independent

interface for creating, monitoring and controlling processes• High level abstraction for process control, breakpoints

and callbacks for process events• DynC API 1.0.1 - Instrumentation language for

specifying snippets• C like instrumentation snippets for easy and more

legible mutator • Handles creation and destruction of snippet-local

variables

35

Page 35: The Deconstruction of  Dyninst : Experiences  and Future Directions

Dyninst 8.0• ProcControl API - Windows and BlueGene• Stackwalker API - Windows and VxWorks• Stackwalker & ProcControl integration into Dyninst

• PatchAPI and integration into Dyninst • SR Dyninst for tamper resistant and obfuscated

binaries• New platforms for binary rewriter

• Dynamically linked binaries on ppc64 and Windows• Statically linked binaries on ppc32 and BlueGene/P

• Dataflow API official release

36

Page 36: The Deconstruction of  Dyninst : Experiences  and Future Directions

MRNet 3.0.1

37

• Support for loading several filters from the same library

• Lightweight MRNet back-end support for non-blocking receives

• CrayXT support for staging files using ALPS tool helper

• Improved build structure that permits configuration for multiple platforms from a single source distribution

• Numerous bug fixes and enhancements

Page 37: The Deconstruction of  Dyninst : Experiences  and Future Directions

38

Software and Manualso Dyninst 7.0.1, MRNet 3.0.1: available

now!o Downloads:

http://www.paradyn.org/html/downloads.htmlhttp://www.paradyn.org/html/manuals.html

o Dyninst 8.0 – 4th quarter, 2011o MRNet 3.0.2 – coming soon!

Page 38: The Deconstruction of  Dyninst : Experiences  and Future Directions

New Environments• Virtual Machines

• Whole-system profiling (guest + VMM) using instrumentation

• VMM-level information to understand how and why an application's performance is affected by the virtualized environment

• Expand performance profiling in the virtualized environment, where traditional approaches do not work or may not be sufficient

• Mobile environments – VxWorks, ARM• GPUs

39

Page 39: The Deconstruction of  Dyninst : Experiences  and Future Directions

Questions

40

Page 40: The Deconstruction of  Dyninst : Experiences  and Future Directions

Unstrip: Semantic Descriptors• We take a semantic approach• Record information that is likely to be

invariant across multiple versions of the function

41unstrip: Restoring Function Information to Stripped Binaries

<accept>:mov %ebx, %edxmov %0x66,%eaxmov $0x5,%ebxlea 0x4(%esp),%ecxint $0x80mov %edx, %ebxcmp %0xffffff83,%eaxjae 8048300retmov %esi,%esi

int $0x80

mov %0x66,%eaxmov $0x5,%ebx

{<socketcall >}

, 5

Page 41: The Deconstruction of  Dyninst : Experiences  and Future Directions

unstrip

Identifying Functions in a Stripped Binary

42unstrip: Restoring Function Information to Stripped Binaries

stripped binary

unstripped

binary

Descriptor Database

For each wrapper function {

1. Build the semantic descriptor.

2. Search the database for a match (two stages).

3. Add label to symbol table.

}

Page 42: The Deconstruction of  Dyninst : Experiences  and Future Directions

43

Performance: Capturing Fine-grained behavior

Introduction to the PatchAPI

User Mutator

DyninstAPI

PatchAPI

find pointinsert snippetdelete snippet

Process

void foo () {

}

void bar () {

}

void baz () {

}

Snippet

Snippet

Snippet

Process

void foo () {

bar()}void bar () {

baz()}void baz () {

}

Instrumenter.so

PatchAPI

Snippet

Snippet

Snippet

Dyninst(3rd party instrumentation)

Self-propelled instrumentation(1st party instrumentation)

Page 43: The Deconstruction of  Dyninst : Experiences  and Future Directions

44

Address Space

Snippet

CFG Parsing

InstrumentationEngine

PluginInterface

PublicInterface

New Component: PatchAPI

Introduction to the PatchAPI

Dyninst Internal

PatchAPI

Page 44: The Deconstruction of  Dyninst : Experiences  and Future Directions

Dyninst

Analysis tool

Dyninst

Dyninst is a toolbox for analysts

Mutator Specifies instrumentation Gets callbacks for runtime

events Builds high-level analysis

program binary7a 77 0e 20 e9 3d e0 09 e8 68 c0 45 be 79 5e 80 89 08 27 c0 73 1c 88 48 6a d8 6a d0 56 4b fe 92 57 af 40 0c b6 f2 64 32 f5 07 b6 66 21

Control flow analyzer

Instrumenter

Data flow analyzer

CFGCFG

45

loop,block,function,instructioninstrument-ation

functionreplace-ment

callstackwalking

forward &backwardslices

loopanalysis

processcontrol

libraryinjection symbol

tablereading,writing

binaryrewriting

machinelanguageparsing

Page 45: The Deconstruction of  Dyninst : Experiences  and Future Directions

What we could do because of components?• SymtabAPI & StackwalkerAPI • DyninstAPI Instrumentor• ROSE semantics engine • Tools we developed - quickly

• Binary rewriter, unstrip

46

Page 46: The Deconstruction of  Dyninst : Experiences  and Future Directions

Componentization• Trade-offs

• Internal requirements vs. external requirements

• Early feedback vs. interface stability• Development time vs. scope• Structured vs. organic

• Lesson learned• Keep the project details where they belong• Change code incrementally• Test new interfaces

47

Page 47: The Deconstruction of  Dyninst : Experiences  and Future Directions

Binary rewriter• Read binary file format from disk• Parse binary code and build CFG• Generate code for instrumentation• Patch code• Emit new binary file

48

SymtabAPI PatchAPIDyninstAPIParseAPI

Page 48: The Deconstruction of  Dyninst : Experiences  and Future Directions

Binary rewriter

49

SymtabAPI

A Dyninst Component

ParseAPI A Dyninst Component

PatchAPI A Dyninst Component

StackwalkerAPI

A Dyninst Component

ProcControlAPI

A Dyninst Component

DataflowAPI A Dyninst

Component

Page 49: The Deconstruction of  Dyninst : Experiences  and Future Directions

Componentization: Design decisions• Define the scope of the component• Balance internal and external user

requirement• Refine the assumptions• Create right level of abstractions• Build from scratch or improve existing

code• Early feedback vs. interface stability

50

libelfSymtabAPI A Dyninst Component

InstructionAPI A Dyninst Component

StackwalkerAPI

A Dyninst Component

PatchAPI

A Dyninst Component

Page 50: The Deconstruction of  Dyninst : Experiences  and Future Directions

DyninstAPIPatchAPI

Dyninst and the components

AST

Binary

ProcessSymtabAPI

Binary

DynCAPI

SymtabAPI

InstructionAPI

ParseAPI

DataflowAPI

StackwalkerAPI

ProcControl

API

CodeGenAPI

SymtabAPI


Recommended