Testing static analysis tools using exploitable buffer overflows from open source code

By Misha Zitser, Richard P. Lippmann, T. Leek. SIGSOFT '04/FSE-12, 2004

308 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

discovRE: Efficient Cross-Architecture Identification of Bugs in Binary Code (2016, methodology): “We also show that we can identify Heartbleed and POODLE vulnerabilities in an Android system image that contains over 130,000 native ARM functions in about 80 milliseconds.”
Modeling and Discovering Vulnerabilities with Code Property Graphs (2014, background): “As a result of this situation, security research has initially focused on statically finding specific types of vulnerabilities, such as flaws induced by insecure library functions [6], buffer overflows [45], integer overflows [40] or insufficient validation of input data [18].”
LAVA: Large-Scale Automated Vulnerability Addition (2016, unknown): “In 2004, Zitser et al. [27] evaluated static buffer overﬂow detectors; their ground truth corpus was painstakingly assembled by hand over the course of six months and consisted of 14 annotated buffer overﬂows with triggering and non-triggering inputs as well as buggy and patched versions of…”