WARNING: This repository contains work-in-progress code for a version of S2E with a current Qemu version. The code might compile and link, but is for sure not functional. Lots of stuff is still missing, other stuff is stubbed. Use only as a study target.
S2E is a platform for writing tools that analyze the properties and behavior of software systems. So far, S2E has been used to develop a comprehensive performance profiler, a reverse engineering tool for proprietary software, and a bug finding tool for both kernel-mode and user-mode binaries. Building these tools on top of S2E took less than 770 LOC and 40 person-hours each.
S2E’s novelty consists of its ability to scale to large real systems, such as a full Windows stack. S2E is based on two new ideas:
Selective symbolic execution, a way to automatically minimize the amount of code that has to be executed symbolically given a target analysis; and
Relaxed execution consistency models, a way to make principled performance/accuracy trade-offs in complex analyses.
These techniques give S2E three key abilities:
to simultaneously analyze entire families of execution paths, instead of just one execution at a time;
to perform the analyses in-vivo within a real software stack—user programs, libraries, kernel, drivers, etc.— instead of using abstract models of these layers; and to operate directly on binaries, thus being able to analyze even proprietary software.
Conceptually, S2E is an automated path explorer with modular path analyzers: the explorer drives the target system down all execution paths of interest, while analyzers check properties of each such path (e.g., to look for bugs) or simply collect information (e.g., count page faults). Desired paths can be specified in multiple ways, and S2E users can either combine existing analyzers to build a custom analysis tool, or write new analyzers using the S2E API.
S2E helps make analyses based on symbolic execution practical for large software that runs in real environments, without requiring explicit modeling of these environments.
Setup instruction and user documentation can be found in the /docs folder, both in RST and HTML format.