Deobfuscation reverse engineering obfuscated code

Sharath K. Udupa, Saumya K. Debray, Matias Madou

Research output: Chapter in Book/Report/Conference proceedingConference contribution

158 Scopus citations

Abstract

In recent years, code obfuscation has attracted attention as a low cost approach to improving software security by making it difficult for attackers to understand the inner workings of proprietary software systems. This paper examines techniques for automatic deobfuscation of obfuscated programs, as a step towards reverse engineering such programs. Our results indicate that much of the effects of code obfuscation, designed to increase the difficulty of static analyses, can be defeated using simple combinations of straightforward static and dynamic analyses, Our results have applications to both software engineering and software security. In the context of software engineering, we show how dynamic analyses can be used to enhance reverse engineering, even for code that has been designed to be difficult to reverse engineer. For software security, our results serve as an attack model for code obfuscators, and can help with the development of obfuscation techniques that are more resilient to straightforward reverse engineering.

Original languageEnglish (US)
Title of host publicationWCRE
Subtitle of host publication12th Working Conference on Reverse Engineering 2005
Pages45-56
Number of pages12
DOIs
StatePublished - 2005
Externally publishedYes
EventWCRE: 12th Working Conference on Reverse Engineering 2005 - Pittsburgh, PA, United States
Duration: Nov 7 2005Nov 11 2005

Publication series

NameProceedings - Working Conference on Reverse Engineering, WCRE
Volume2005
ISSN (Print)1095-1350

Other

OtherWCRE: 12th Working Conference on Reverse Engineering 2005
Country/TerritoryUnited States
CityPittsburgh, PA
Period11/7/0511/11/05

ASJC Scopus subject areas

  • General Engineering

Fingerprint

Dive into the research topics of 'Deobfuscation reverse engineering obfuscated code'. Together they form a unique fingerprint.

Cite this