Testing static analysis tools using exploitable buffer overflows from open source code
Misha Zitser, Richard P. Lippmann, Tim Leek · ACM SIGSOFT International Symposium on Foundations of Software Engineering (FSE) · 2004
Five modern static analysis tools (ARCHER, BOON, Poly-Space C Verifier, Splint, and UNO) were evaluated using source code examples containing 14 exploitable buffer overflow vulnerabilities found in various versions of Sendmail, BIND, and WU-FTPD. Each code example included a "BAD" case with and a "OK" case without buffer overflows. Buffer overflows varied and included stack, heap, bss and data buffers; access above and below buffer bounds; access using pointers, indices, and functions; and scope differences between buffer creation and use. Detection rates for the "BAD" examples were low except for Poly-Space and Splint which had average detection rates of 87% and 57%, respectively. However, average false alarm rates were high and roughly 50% for these two tools. On patched programs these two tools produce one warning for every 12 to 46 lines of source code and neither tool appears able to accurately distinguished between vulnerable and patched code.
Cited by 226 works. doi:10.1145/1029894.1029911
Authors
References
- The C Programming Language
- StackGuard: Automatic Adaptive Detection and Prevention of Buffer-Overflow Attacks
- A First Step Towards Automated Detection of Buffer Overrun Vulnerabilities.
- The University of California
- ESP
- The Spread of the Sapphire/Slammer Worm
- Static determination of dynamic properties of programs
- Interprocedural may-alias analysis for pointers
- Improving security using extensible lightweight static analysis
- ITS4: a static vulnerability scanner for C and C++ code