Skip to content

Latest commit

 

History

History
86 lines (48 loc) · 2.78 KB

README.md

File metadata and controls

86 lines (48 loc) · 2.78 KB
Raw

The Relevance of Classic Fuzz Testing: Have We Solved This One?

Description

This work is a revisit to Prof. Miller's previous fuzzing works, i.e., 1990, 1995 and 2006. We applied original fuzzing techniques to command-line utilities on multiple platforms and found that 9 crash or hang out of 74 utilities on Linux, 15 out of 78 utilities on FreeBSD, and 12 out of 76 utilities on MacOS. We found that the failure rates of command-line utilities are higher than those in previous studies. We also provided detailed bug analysis, including when a bug was introduced and when it was solved. Some of the errors that we found have been present in the codebase for many years. Plus, we fuzzed core utilities implemented in Rust.

Code

In this study, we updated the source code used in the original fuzzing study. Now it applies to Linux, OS X and FreeBSD.

./src

In this directory:

Makefile

​ To build fuzz.c and ptyjig.c, run:

​ cd ./src && make all

fuzz.c

​ A random string generator.

​ For the usage, run:

​ man ./doc/fuzz.man.

ptyjig.c

​ A tool to provide input to utilities that read input from the terminal, it is used to test programs such as vim and bash.

​ For the usage, run:

​ man ./doc/ptyjig.man.

./run_test

In this directory:

./test_Linux/

​ Name and option pools of each cmd to be tested on Linux.

./test_MacOS/

​ Name and option pools of each cmd to be tested on MacOS.

./test_FreeBSD/

​ Name and option pools of each cmd to be tested on FreeBSD.

./end/

​ For each program tested with ptyjig, we specify a string to append to the random input to attempt to terminate the utility. For example, when testing vim, we append the sequence “ESC :q !”. In this way we can distinguish if the program is waiting for more input after the end of random input from a program that is hung.

run.py

​ Automatic script to test all utilities listed in a configuration file(see ./test_Linux/ or ./test_MacOS/ or ./test_FreeBSD/).

​ For the usage, run:

​ man ./doc/run.py.1.

./generate_test

Python scripts to generate random files.

./doc

Man pages for the above files.

Reference

If you find this implementation useful in your research, please consider citing:

@article{miller2020relevance,
  title={The Relevance of Classic Fuzz Testing: Have We Solved This One?},
  author={Miller, Barton and Zhang, Mengxiao and Heymann, Elisa},
  journal={IEEE Transactions on Software Engineering},
  year={2020},
  publisher={IEEE}
}