libFuzzer Integration Reference

Supported Platforms and Configurations

Linux

Linux is fully supported by libFuzzer and ClusterFuzz with following sanitizer configurations:

GN ArgumentDescription
is_asan=trueenables Address Sanitizer to catch problems like buffer overruns.
is_msan=trueenables Memory Sanitizer to catch problems like uninitialed reads.
is_ubsan_security=trueenables Undefined Behavior Sanitizer to catch[1] undefined behavior like integer overflow.

Configuration example:

# With address sanitizer
gn gen out/libfuzzer '--args=use_libfuzzer=true is_asan=true enable_nacl=false' --check

Mac

Mac is experimentally supported by libFuzzer with is_asan configuration. Mac support is not provided by ClusterFuzz.

Configuration example:

gn gen out/libfuzzer '--args=use_libfuzzer=true is_asan=true enable_nacl=false mac_deployment_target="10.7"' --check

fuzzer_test GN Template

Use fuzzer_test to define libFuzzer targets:

fuzzer_test("my_fuzzer") {
  ...
}

Following arguments are supported:

ArgumentDescription
sourcesrequired list of fuzzer test source files.
depsfuzzer dependencies
additional_configsadditional GN configurations to be used for compilation
dicta dictionary file for the fuzzer
libfuzzer_optionsruntime options file for the fuzzer. See Fuzzer Runtime Options

Fuzzer Runtime Options

There are many different runtime options supported by libFuzzer. Options are passed as command line arguments:

./fuzzer [-flag1=val1 [-flag2=val2 ...] ] [dir1 [dir2 ...] ]

Most common flags are:

FlagDescription
max_lenMaximum length of test input.
timeoutTimeout of seconds. Units slower than this value will be reported as bugs.

A fuller list of options can be found at libFuzzer Usage page and by running the binary with -help=1.

To specify these options for ClusterFuzz, list all parameters in libfuzzer_options target attribute:

fuzzer_test("my_fuzzer") {
  ...
  libfuzzer_options = [
    "max_len=2048",
    "use_traces=1",
  ]
}