Fuzz introspector
For issues and ideas: https://github.com/ossf/fuzz-introspector/issues

Project functions 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.

For further technical details on the meaning of columns in the below table, please see the Glossary .

Func name Functions filename Args Function call depth Reached by Fuzzers Runtime reached by Fuzzers Combined reached by Fuzzers Fuzzers runtime hit Func lines hit % I Count BB Count Cyclomatic complexity Functions reached Reached by functions Accumulated cyclomatic complexity Undiscovered complexity

Fuzzer details

Fuzzer: config_read_fuzzer

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is
Color Runtime hitcount Callsite count Percentage
red 0 195 46.3%
gold [1:9] 11 2.61%
yellow [10:29] 4 0.95%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 211 50.1%
All colors 421 100

Fuzz blockers

The followings are the branches where fuzzer fails to bypass.

Unique non-covered Complexity Unique Reachable Complexities Unique Reachable Functions All non-covered Complexity All Reachable Complexity Function Name Function Callsite Blocked Branch
103 103 8 :

['__errno_location', 'libconfig_yyrealloc', 'getc', 'fread', 'ferror', 'yy_fatal_error', 'libconfig_yyrestart', 'clearerr']

103 103 yy_get_next_buffer call site: 00145 /src/libconfig/build/lib/scanner.c:1823
45 45 1 :

['libconfig_yyrestart']

45 660 __config_read call site: 00029 /src/libconfig/lib/libconfig.c:576
4 4 2 :

['fopen', 'fclose']

4 4 libconfig_scanctx_next_include_file call site: 00108 /src/libconfig/lib/scanctx.c:130
2 2 1 :

['abort']

2 2 open_null_file call site: 00002 /src/libconfig/fuzz/fuzz_config_read.c:33
2 2 1 :

['fputc']

2 2 __config_indent call site: 00357 /src/libconfig/lib/libconfig.c:147
2 2 2 :

['fclose', 'free']

2 2 libconfig_scanctx_pop_include call site: 00111 /src/libconfig/lib/scanctx.c:162
2 2 1 :

['__errno_location']

2 2 libconfig_yylex_init_extra call site: 00032 /src/libconfig/build/lib/scanner.c:2687
0 91 2 :

['__config_setting_create', 'config_setting_remove']

0 91 config_setting_add call site: 00171 /src/libconfig/lib/libconfig.c:1942
0 8 1 :

['config_setting_get_elem']

0 16 config_setting_set_string_elem call site: 00281 /src/libconfig/lib/libconfig.c:1808
0 8 1 :

['config_setting_get_elem']

0 14 config_setting_set_int64_elem call site: 00223 /src/libconfig/lib/libconfig.c:1658
0 8 1 :

['config_setting_get_elem']

0 13 config_setting_set_float_elem call site: 00270 /src/libconfig/lib/libconfig.c:1705
0 8 1 :

['config_setting_get_elem']

0 12 config_setting_set_int_elem call site: 00212 /src/libconfig/lib/libconfig.c:1610

Runtime coverage analysis

Covered functions
96
Functions that are reachable but not covered
40
Reachable functions
136
Percentage of reachable functions covered
70.59%
NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.
Function name source code lines source lines hit percentage hit

Files reached

filename functions hit
fuzz/fuzz_config_read.c 3
lib/libconfig.c 51
lib/strvec.c 3
lib/util.c 7
fuzz/fuzz_data.c 2
lib/scanctx.c 7
build/lib/scanner.c 24
build/lib/scanner.l 2
build/lib/grammar.c 2
lib/strbuf.c 4
build/lib/grammar.y 2

Files and Directories in report

This section shows which files and directories are considered in this report. The main reason for showing this is fuzz introspector may include more code in the reasoning than is desired. This section helps identify if too many files/directories are included, e.g. third party code, which may be irrelevant for the threat model. In the event too much is included, fuzz introspector supports a configuration file that can exclude data from the report. See the following link for more information on how to create a config file: link

Files in report

Source file Reached by Covered by
[] []
/src/libconfig/build/lib/grammar.y ['config_read_fuzzer'] ['config_read_fuzzer']
/src/libconfig/lib/libconfig.c ['config_read_fuzzer'] ['config_read_fuzzer']
/src/libconfig/build/lib/scanner.l ['config_read_fuzzer'] ['config_read_fuzzer']
/src/libconfig/lib/strbuf.c ['config_read_fuzzer'] ['config_read_fuzzer']
/src/libconfig/build/lib/scanner.c ['config_read_fuzzer'] ['config_read_fuzzer']
/src/libconfig/lib/strvec.c ['config_read_fuzzer'] ['config_read_fuzzer']
/src/libconfig/fuzz/fuzz_config_read.c ['config_read_fuzzer'] ['config_read_fuzzer']
/src/libconfig/build/lib/grammar.c ['config_read_fuzzer'] ['config_read_fuzzer']
/src/libconfig/lib/util.c ['config_read_fuzzer'] ['config_read_fuzzer']
/src/libconfig/fuzz/fuzz_data.c ['config_read_fuzzer'] ['config_read_fuzzer']
/src/libconfig/lib/scanctx.c ['config_read_fuzzer'] ['config_read_fuzzer']

Directories in report

Directory
/src/libconfig/fuzz/
/src/libconfig/build/lib/
/src/libconfig/lib/