Tigress is a diversifying virtualizer/obfuscator for the C language that supports many novel defenses against both static and dynamic reverse engineering and de-virtualization attacks.In particular, Tigress protects against static de-virtualization by generating virtual instruction sets of arbitrary complexity and diversity, by producing interpreters with multiple types of instruction dispatch, and by inserting code for anti alias analysis. Tigress protects against dynamic de-virtualization by merging the real code with bogus functions, by inserting implicit flow, and by creating slowly-executing reenetrant interpreters. Tigress implements its own version of code packing through the use of runtime code generation. Finally, Tigress' dynamic transformation provides a generalized form of continous runtime code modification.
- Sebastian Millius solved challenge 0000!
- New question-mark opaque predicates in AddOpaque.
- New program array encoding now supported in Virtualize! There are also new opaque expressions that are input dependent to confuse taint analysis.
- New dynamic transformation that implements our generalization of previously proposed dynamic obfuscation schemes.
- The slides from my Eurocrypt 2016 invited talk are here. The talk itself is here.
- Please consider attending The 7th International Summer School on Information Security and Protection (ISSISP'16) which will be held on Aug 2-6 in Amrita School of Engineering, Amritapuri, Kollam, Kerala, India, and 6-8 in Bangalore.
Tigress supports all of the C99 language, including gcc extensions. The source-to-source design means that the transformed code can be easily examined, which is useful in a pedagogical setting. Also, Tigress' output, once compiled and stripped of symbols, is a good target for reverse engineering and de-virtualization exercises. Tigress' design is similar to that of commercial tools, such as Cloakware/IRDETO's C/C++ Transcoder.
The user interacts with Tigress by giving an input C file, a seed, and a sequence of transformations:
Tigress supports three major transformations:
- Virtualization, i.e. transforming a function into an interpreter whose bytecode language is specialized for this function, and
- Jitting, i.e. transforming a function into one that generates its machine code at runtime.
- Dynamic, i.e. transforming a function into one that continously modifies its machine code at runtime.
In addition, Tigress has a collection of supporting transformations that can help with resilience to attack, diversity, and stealth:
- Control flow flattening,
- function Splitting, Merging, and Argument randomization,
- Control flow splitting with opaque predicates,
- encoding of Literals, Data, and Arithmetic.
Tigress also supports three transformations designed to thwart particular static and dynamic analyses:
Tigress is designed such that, from a single source program, it is possible to generate large numbers of highly diversified variants. This diversity is both static and dynamic, i.e. two variants will differ both in their machine code and in the resulting instruction traces. In essence, every decision Tigress makes is dependent on a randomization seed, controllable by the user. There are two major sources of diversity:
- Tigress goes to great lengths to provide as many variants of each transformation as possible. For example, our virtualization transformation supports eight kinds of dispatch, can generate arbitrarily complex virtual instruction sets, and can generate instructions which arbitrarily mix stack and register operands.
- Tigress' transformations can be combined in arbitrary ways, such as virtualizing a virtualized function, jit two merged functions, virtualize a jitted function, etc.
Research: Tigress was originally designed as the backend of a system for remote attestation. The idea was to force rapid updates to the code running on an untrusted remote site in order to increase the workload of the attacker who has to crack, and re-crack, the code as it is constantly updated.
Other applications of Tigress include:
- We are currently using Tigress to measure the stealth of obfuscated code.
- One group is using Tigress to develop A Framework for Measuring Software Obfuscation Resilience Against Automated Attacks.
- Another group is using Tigress to test code stylometric algorithms.
- Federico Scrinzi is using Tigress to generate obfuscated code to analyze in his University of Twente Master's Thesis Behavioral Analysis of Obfuscated Code.
- Mark Janssen's Master's Thesis Combining learning with fuzzing for software deobfuscation uses Tigress to generate obfuscated code to analyze.
- Johannes Kinder is using Tigress to study static analysis of virtualized code, Towards Static Analysis of Virtualization-Obfuscated Binaries, WCRE'12.
- In their paper Trading Off a Vulnerability: Does Software Obfuscation Increase the Risk of ROP published in the Journal of Cyber Security and Mobility Harshvardhan P. Joshi, Aravindhan Dhanasekaran and Rudra Dutta use Tigress for evaluation purposes.
- Pierre Graux uses Tigress to study de-virtualization in his paper Désobscurcissement de programmes virtualisés.
Benchmarking: We are planning to use Tigress to generate collections of software protection benchmark programs. These will provide the community with randomly generated attack targets to form a basis for uniform and generally accepted evaluation procedures for software protection algorithms. In particular, we are hoping future de-virtualization research projects will use Tigress-generated interpreters as one of their attack targets.
Challenges: To stimulate reverse engineering research, we are publishing sets of challenge problems generated by Tigress. Prizes will be awarded to those who are first to crack.
Education. In our classes we use Tigress to generate reverse engineering exercises and take-home exams for the students. We use Tigress' RandomFuns transformation to generate a unique random program for every student in the class and protect it using some appropriate combination of transformations. The difficulty of the exercises can be easily varied by picking different sequences of transformations, and, since diversity guarantees that every program instance is unique, cheating is made more difficult.