High level conclusions

Reachability and coverage overview

The following table shows data about each function in the project. The functions included in this table correspond to all functions that exist in the executables of the fuzzers. As such, there may be functions that are from third-party libraries.

Fuzzer: fuzz_http.c

Call tree

Fuzzer: fuzz_hpack_decode.c

Call tree

Fuzzer: fuzz_h1_parse.c

Call tree

Fuzzer: fuzz_cfg_parser.c

Call tree

Fuzzer: fuzz_h1_htx.c

Call tree

Optimal target analysis

Remaining optimal interesting functions

The following table shows a list of functions that are optimal targets. Optimal targets are identified by finding the functions that in combination, yield a high code coverage.

Implementing fuzzers that target the above functions will improve reachability such that it becomes:

All functions overview

If you implement fuzzers for these functions, the status of all functions in the project will be:

This sections provides heuristics that can be used as input to a fuzz engine when running a given fuzz target. The current focus is on providing input that is usable by libFuzzer.

fuzz_http.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

fuzz_hpack_decode.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

fuzz_h1_parse.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

fuzz_cfg_parser.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

fuzz_h1_htx.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

New fuzzers

The below fuzzers are templates and suggestions for how to target the set of optimal functions above

haproxy.c

#include "ada_fuzz_header.h"

int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
  af_safe_gb_init(data, size);

  /* target read_cfg_in_discovery_mode */
  int new_var0 = ada_safe_get_int();
  char **new_var1 = af_get_double_char_p();
  read_cfg_in_discovery_mode(new_var0, new_var1);

  af_safe_gb_cleanup();
}

Files in report

Directories in report

This section shows a list of 3rd party function calls and their relative coverage information. By static analysis of the target project code, all of the 3rd party function call and their caller information, including the source file and line number that initiate the call are captured. The caller source code file and line number are shown in column 2 while column 1 is the function name of the 3rd party function call. Each occurrent of the 3rd party function call will occuply a separate row. Column 3 of each row indicate if the 3rd party call in the source file line is unreachable. Column 4 lists all fuzzers that have covered that particular system call in that specific location (source file and line)during their dynamic fuzzing.

Function in each files in report

This section contains multiple tables, each table contains a list of sink functions/methods found in the project for one of the CWE supported by the sink analyser, together with information like which fuzzers statically reach the sink functions/methods and possible call path to that sink functions/methods if it is not statically reached by any fuzzers. Column 1 is the function/method name of the sink functions/methods found in the project. Column 2 lists all fuzzers (or no fuzzers at all) that have covered that particular function method statically. Column 3 shows a list of possible call paths to reach the specific function/method call if none of the fuzzers cover the target function/method calls. Lastly, column 4 shows possible fuzzer blockers that prevent an existing fuzzer from reaching the target sink functions/methods dynamically.

Sink functions/methods found for CWE787