Skip to content

whitepoet/fuzzer-test-suite

This branch is 2 commits behind google/fuzzer-test-suite:master.

Folders and files

NameName
Last commit message
Last commit date
Feb 7, 2020
Feb 7, 2020
Dec 1, 2017
Jul 9, 2019
Sep 27, 2019
Feb 7, 2020
Oct 28, 2019
Oct 28, 2019
Oct 17, 2019
Feb 7, 2020
Feb 7, 2020
Feb 7, 2020
Feb 7, 2020
Mar 9, 2020
Feb 7, 2020
Oct 28, 2019
Oct 28, 2019
Oct 28, 2019
Mar 2, 2018
Feb 7, 2020
Feb 7, 2020
Feb 7, 2020
Feb 7, 2020
Oct 28, 2019
Sep 27, 2019
Oct 28, 2019
Oct 28, 2019
Mar 1, 2018
Oct 7, 2016
Oct 7, 2016
Oct 7, 2016
Mar 20, 2020
Oct 7, 2016
Feb 7, 2020
Jun 12, 2018
Jul 28, 2017

Repository files navigation

fuzzer-test-suite

NOTE: For most use cases, fuzzer-test-suite is superseded by FuzzBench. We recommend using FuzzBench for all future fuzzer benchmarking. FuzzBench is based on many of the same ideas as FTS, such as realistic benchmarks (it actually uses some benchmarks from FTS) but has many improvements such as a free service and a design that makes adding new fuzzers and new benchmarks easier.

This is a set of tests (benchmarks) for fuzzing engines (fuzzers).

The goal of this project is to have a set of fuzzing benchmarks derived from real-life libraries that have interesting bugs, hard-to-find code paths, or other challenges for bug finding tools.

In addition, this project provides a fuzzing engine comparison framework to execute A/B tests between different fuzzing configurations.

The current version supports libFuzzer and AFL. In future versions we may support other fuzzing engines.

See also

Contributing

See CONTRIBUTING first. If you want to add one more benchmark to the test suite, simply mimic one of the existing benchmarks and send the pull request.

Disclaimer

This is not an official Google product.

About

Set of tests for fuzzing engines

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • C 98.4%
  • Other 1.6%