1 / 25

Deobfuscation of Virtualization-Obfuscated Software

Deobfuscation of Virtualization-Obfuscated Software. Kevin Coogan , Gen Lu, saumya debray Department of Comuputer Science University of Arizona 報告者:張逸文. Outline. Introduction Deobfuscation Experimental Evaluation Related Work Conclusion. Introduction ( 1/4 ).

duante
Download Presentation

Deobfuscation of Virtualization-Obfuscated Software

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Deobfuscation of Virtualization-Obfuscated Software Kevin Coogan, Gen Lu, saumyadebray Department of Comuputer Science University of Arizona 報告者:張逸文 ADLab

  2. Outline Introduction Deobfuscation Experimental Evaluation Related Work Conclusion ADLab

  3. Introduction(1/4) • Basic about Reverse Engineering • Compilation • Decompilation ADLab

  4. Introduction(2/4) • Virtualization obfuscators • VMProtect, Code Virtualizer { VIRTUALIZER_START your code VIRTUALIZER_END } ADLab

  5. Introduction(3/4) • The virtualization-obfuscated programs are resistant to static and dynamic analysis techniques • The executed code reveals only the structure and logic of the byte-code interpreter • Randomness VM • Outside-in approach • Reverse engineer the VM interpreter • Individual byte code instructions • Recover the logic • The structure of the interpreter meets certain requirements ADLab

  6. Introduction(4/4) Programs interact with the system through system calls Identifying instructions that interact with the system Not recovering the original instructions Capturing behavior of the code General, using in a wide range ADLab

  7. Deobfuscation Static analysis v.s dynamic trace Identifying instructions that are known to be part of the original code No information about the specific structure of the interpreter ADLab

  8. Deobfuscation • Overall approach: • Tracing tool • Low level execution trace • Identifying system calls and their arguments • database • Instruction trace • Relevant instructions • Building a subtrace • Relevant subtrace ADLab

  9. Deobfuscation • Value-based Dependence Analysis • Not recovering the original code • The process of deobfuscation must be semantics-preserving • Identifying instructions that affect the values of the arguments to system calls • Slicing algorithms --- control-dependent • Data dependencies • Use-definition chains --- link instructions that use a variable to the instruction that define it • Problem: ADLab

  10. Deobfuscation • Value-based dependence if( I defines a location l S) { I is marked as relevant; l is removed from S; the set of locations used by I is added to S; } • Problem:a pointer to a structure I uses some locations  l1, l2, … , ld if ( I uses li P to define ld ) ld is added to P if ( li access a memory location ) [li ] is added to M ADLab

  11. Deobfuscation • Relevant Conditional Control Flow • Value-based dependence analysis doesn’t identify the associated control flow instructions • The occurring of conditional control flow • IA-32 architecture  setting the condition code flags in the eflags register • Not such simple!! • Examining target address • EquationalResoning System:translate each instruction in the dynamic trace into an equivalent set of equations ADLab

  12. Deobfuscation • EquationalResoning System • Identifies conditional dependencies • The left hand side variables in an equation is numbered by the order of its instruction appears • The right hand side variables is numbered by the instruction that defined it • Example 1. ADLab

  13. Deobfuscation • Example 2. • Example 3. • Indirect jump ADLab

  14. Deobfuscation • Example 4. • Used in VMProtect Target20 = index1*4+0x10000 ADLab

  15. Deobfuscation ADLab

  16. Deobfuscation ADLab

  17. Deobfuscation • Relevant Call-Return Control Flow • Identifying functions:the behavior of calls and returns • Knowing how them work allows one to use for other purposes • Behavior of Function Calls and Returns ADLab

  18. Deobfuscation call 改成push 無法解決 registers ADLab

  19. Deobfuscation • Identification Approach • Call:a code address is saved at the call site • Return:the saved address is used for a control transfer at the return point ADLab

  20. Deobfuscation Relevant Dynamic Trace ADLab

  21. Experimental Evaluation • Experimental Methodology • Compile original source code • Generate an original dynamic trace • Build an original subtrace • Virtualization-obfuscation technique • Generate an obfuscated dynamic trace • Build a relevant subtrace of the obfuscated subtrace • The obfuscated subtrace is matched to the original subtrace and scores are produced • The relevance score and obfuscation score are calculated ADLab

  22. Experimental Evaluation VX Heavens website ADLab

  23. Related Work • Deobfuscation of code obfuscated via virtualization obfuscators • Rolles, Sharif, Falliere • Programming language community • Partial evaluation ADLab

  24. Conclusions Virtualization-obfuscated programs are difficult to reverse engineer We present a different approach to identifying the flow of values to system call instructions ADLab

  25. XD ~ ADLab

More Related