System emulation and firmware re-hosting have become popular techniques to answer
various security and performance related questions, such as determining whether a …

Binary rewriting is changing the semantics of a program without having the source code at
hand. It is used for diverse purposes, such as emulation (eg, QEMU), optimization (eg …

Analyzing the security of closed source binaries is currently impractical for end-users, or
even developers who rely on third-party libraries. Such analysis relies on automatic …

Coverage-guided fuzzing is one of the most successful approaches for discovering software
bugs and security vulnerabilities. Of its three main components:(1) test case generation,(2) …

For comprehensive analysis of all executable code, and fast turn-around time for
transformations, it is essential to operate directly on binaries to enable profiling, security …

Disassembly of binary code is hard, but necessary for improving the security of binary
software. Over the past few decades, research in binary disassembly has produced many …

Commodity software typically includes functionalities for a broad user population. However,
each individual user usually only needs a subset of the supported functionalities. The …

Static binary rewriting is a core technology for many systems and security applications,
including profiling, optimization, and software fault isolation. While many static binary …

Coverage-guided fuzzing is one of the most effective software security testing techniques.
Fuzzing takes on one of two forms: compiler-based or binary-only, depending on the …

Closely monitoring the behavior of a software system during its execution enables
developers and analysts to observe, and ultimately understand, how it works. This kind of …