Fuzzing introspection testcases

Test a fuzzer what fuzzing challenges it can solve. The goal is to have testcases that afl++ can all complete - once they are all implemented. Currently the different solving mechanisms have to be set as defined in src/afl-fuzz-redqueen.c. The comparisons to honggfuzz and libfuzzer are biased, as the testcases are how afl-fuzz sees things. The libfuzzer/ directories has libfuzzer's applicable own testcases, of which afl++ is only able to solve 64% (vs 86% honggfuzz and 92% libfuzzer).

Setup

The fuzzers and necessary compilers must be in the path: afl-clang-fast, afl-fuzz, hfuzz-clang, honggfuzz, clang.

Running

./test.sh TARGET [SPECIFIC_TESTCASE]

TARGET can be (currently) one of:

• afl++
• afl++-qemu
• afl++-frida
• libafl (WIP)
• honggfuzz
• libfuzzer
• kirenenko (via test-kirenenko.sh, use it's docker container)
• symcc + qemu (via test-symcc.sh and test-symqemu.sh, use it's docker container)
• manticore (via test-manticore.sh)

Note that manticore and symqemu success can depend on compile options.

Testcases:

• test-u8 - several chained 8 bits checks
• test-u16 - several chained 16 bits checks
• test-u32 - several chained 32 bits checks
• test-u64 - several chained 64 bits checks
• test-u128 - several chained 128 bits checks
• test-u32-cmp - several chained 32 bit lesser/greater checks
• text-extint - llvm _ExtInt() tests
• test-float - several chained float checks
• test-double - several chained double checks
• test-longdouble - several chained long double checks
• test-memcmp - several chained memcmp checks
• test-strcmp - several chained strncasecmp checks
• test-transform - different transforming string checks
• test-crc32 - several chained crc32 checks

The testcases are WIP - some might be further refined in the future and more added.

Results

On success the time to solve is displayed.

On failure the generated corpus files are displayed (so you can see how many finds there were). There is also an output log called TESTCASE.log.

Test as of July 2022

All from current repository state (afl++ is CMPLOG instrumented and afl-fuzz -l3AT -Z). Solve time: 120 seconds for afl++/honggfuzz/libfuzzer Sym*, Kirenenko and Manticore are not fuzzers but solvers, hence no time restriction. SymCC and SymQEMU have the same results so they are combined to save space.

afl++ has the most solves, but due to the many solve attempts overall fuzzing performance is decreased, as can be seen at https://www.fuzzbench.com/reports/experimental/2021-01-12-aflpp/. Interpretation: the slowest solver is the best in real-world fuzzing.

More testcases or fuzzers?

Just add them and send a PR.