High level conclusions

Fuzzers reach 61.89% of cyclomatic complexity.

Fuzzers reach 41.07% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

69 / 168

Cyclomatic complexity statically reachable by fuzzers

1314 / 2123

Runtime code coverage of functions

71 / 168

Warning: The number of runtime covered functions are larger than the number of reachable functions. This means that Fuzz Introspector found there are more functions covered at runtime than what is considered reachable based on the static analysis. This is a limitation in the analysis as anything covered at runtime is by definition reachable by the fuzzers.
This is likely due to a limitation in the static analysis. In this case, the count of functions covered at runtime is the true value, which means this is what should be considered "achieved" by the fuzzer.

Use the project functions table below to query all functions that were not covered at runtime.

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	Fuzzers runtime hit	Func lines hit %	I Count	BB Count	Cyclomatic complexity	Functions reached	Reached by functions	Accumulated cyclomatic complexity	Undiscovered complexity

Fuzzer: checksum_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	5	100.%
All colors	5	100

Runtime coverage analysis

Covered functions

3

Functions that are reachable but not covered

0

Reachable functions

3

Percentage of reachable functions covered

100.0%

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
tests/checksum_fuzzer.c	1
build/amalgamation/miniz.c	2

Fuzzer: flush_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	3	7.89%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	35	92.1%
All colors	38	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
0	268	1 : View List ['tdefl_compress_block']	0	268	tdefl_flush_block	call site: 00016	/src/miniz/build/amalgamation/miniz.c:1325
0	0	None	4	8	test_flush	call site: 00034	/src/miniz/tests/flush_fuzzer.c:53
0	0	None	0	834	tdefl_compress	call site: 00012	/src/miniz/build/amalgamation/miniz.c:1944
0	0	None	0	371	tdefl_compress_normal	call site: 00014	/src/miniz/build/amalgamation/miniz.c:1832
0	0	None	0	371	tdefl_compress_normal	call site: 00014	/src/miniz/build/amalgamation/miniz.c:1859
0	0	None	0	0	tdefl_compress	call site: 00012	/src/miniz/build/amalgamation/miniz.c:1915
0	0	None	0	0	tdefl_compress	call site: 00012	/src/miniz/build/amalgamation/miniz.c:1933
0	0	None	0	0	tdefl_compress	call site: 00014	/src/miniz/build/amalgamation/miniz.c:1958
0	0	None	0	0	tdefl_compress	call site: 00030	/src/miniz/build/amalgamation/miniz.c:1967
0	0	None	0	0	tdefl_create_comp_flags_from_zip_params	call site: 00008	/src/miniz/build/amalgamation/miniz.c:2115
0	0	None	0	0	tdefl_create_comp_flags_from_zip_params	call site: 00008	/src/miniz/build/amalgamation/miniz.c:2117
0	0	None	0	0	tdefl_create_comp_flags_from_zip_params	call site: 00008	/src/miniz/build/amalgamation/miniz.c:2119

Runtime coverage analysis

Covered functions

29

Functions that are reachable but not covered

3

Reachable functions

27

Percentage of reachable functions covered

88.89%

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.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
tests/flush_fuzzer.c	2
build/amalgamation/miniz.c	22

Fuzzer: uncompress_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	1	9.09%
gold	[1:9]	1	9.09%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	9	81.8%
All colors	11	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
0	0	None	0	198	mz_inflate	call site: 00005	/src/miniz/build/amalgamation/miniz.c:467
0	0	None	0	3	tinfl_decompress	call site: 00006	/src/miniz/build/amalgamation/miniz.c:2479
0	0	None	0	0	tinfl_decompress	call site: 00006	/src/miniz/build/amalgamation/miniz.c:2451
0	0	None	0	0	tinfl_decompress	call site: 00007	/src/miniz/build/amalgamation/miniz.c:2854

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

0

Reachable functions

9

Percentage of reachable functions covered

100.0%

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.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
tests/uncompress_fuzzer.c	1
build/amalgamation/miniz.c	8

Fuzzer: compress_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	4	7.54%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	49	92.4%
All colors	53	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
0	496	2 : View List ['tdefl_get_adler32', 'tdefl_compress']	0	496	mz_deflate	call site: 00032	/src/miniz/build/amalgamation/miniz.c:282
0	268	1 : View List ['tdefl_compress_block']	0	268	tdefl_flush_block	call site: 00016	/src/miniz/build/amalgamation/miniz.c:1325
0	0	None	0	834	tdefl_compress	call site: 00012	/src/miniz/build/amalgamation/miniz.c:1944
0	0	None	0	198	mz_inflate	call site: 00039	/src/miniz/build/amalgamation/miniz.c:467
0	0	None	0	5	tdefl_compress	call site: 00030	/src/miniz/build/amalgamation/miniz.c:1970
0	0	None	0	4	mz_compress2	call site: 00011	/src/miniz/build/amalgamation/miniz.c:339
0	0	None	0	3	tinfl_decompress	call site: 00040	/src/miniz/build/amalgamation/miniz.c:2479
0	0	None	0	0	tdefl_compress	call site: 00012	/src/miniz/build/amalgamation/miniz.c:1915
0	0	None	0	0	tdefl_compress	call site: 00012	/src/miniz/build/amalgamation/miniz.c:1933
0	0	None	0	0	tdefl_compress	call site: 00014	/src/miniz/build/amalgamation/miniz.c:1958
0	0	None	0	0	tdefl_compress	call site: 00030	/src/miniz/build/amalgamation/miniz.c:1967
0	0	None	0	0	tdefl_create_comp_flags_from_zip_params	call site: 00009	/src/miniz/build/amalgamation/miniz.c:2115

Runtime coverage analysis

Covered functions

40

Functions that are reachable but not covered

3

Reachable functions

38

Percentage of reachable functions covered

92.11%

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.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
tests/compress_fuzzer.c	4
build/amalgamation/miniz.c	31

Fuzzer: uncompress2_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	1	10.0%
gold	[1:9]	1	10.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	8	80.0%
All colors	10	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
0	0	None	0	198	mz_inflate	call site: 00004	/src/miniz/build/amalgamation/miniz.c:467
0	0	None	0	3	tinfl_decompress	call site: 00005	/src/miniz/build/amalgamation/miniz.c:2479
0	0	None	0	0	tinfl_decompress	call site: 00005	/src/miniz/build/amalgamation/miniz.c:2451
0	0	None	0	0	tinfl_decompress	call site: 00006	/src/miniz/build/amalgamation/miniz.c:2854

Runtime coverage analysis

Covered functions

10

Functions that are reachable but not covered

0

Reachable functions

8

Percentage of reachable functions covered

100.0%

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.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
tests/uncompress2_fuzzer.c	1
build/amalgamation/miniz.c	7

Fuzzer: zip_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	11	19.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	46	80.7%
All colors	57	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
0	0	None	6	6	mz_zip_reader_locate_file_v2	call site: 00043	/src/miniz/build/amalgamation/miniz.c:4505
0	0	None	2	2	mz_zip_reader_end_internal	call site: 00012	/src/miniz/build/amalgamation/miniz.c:3986
0	0	None	0	272	mz_zip_reader_extract_to_mem_no_alloc1	call site: 00050	/src/miniz/build/amalgamation/miniz.c:4571
0	0	None	0	205	mz_zip_reader_extract_to_mem_no_alloc1	call site: 00052	/src/miniz/build/amalgamation/miniz.c:4627
0	0	None	0	205	mz_zip_reader_extract_to_mem_no_alloc1	call site: 00052	/src/miniz/build/amalgamation/miniz.c:4662
0	0	None	0	3	tinfl_decompress	call site: 00033	/src/miniz/build/amalgamation/miniz.c:2474
0	0	None	0	0	tinfl_decompress	call site: 00033	/src/miniz/build/amalgamation/miniz.c:2451
0	0	None	0	0	mz_zip_reader_get_filename	call site: 00038	/src/miniz/build/amalgamation/miniz.c:7867
0	0	None	0	0	mz_zip_reader_end_internal	call site: 00012	/src/miniz/build/amalgamation/miniz.c:4004
0	0	None	0	0	mz_zip_reader_extract_to_mem_no_alloc1	call site: 00054	/src/miniz/build/amalgamation/miniz.c:4699
0	0	None	0	0	mz_zip_array_ensure_capacity	call site: 00008	/src/miniz/build/amalgamation/miniz.c:3381

Runtime coverage analysis

Covered functions

42

Functions that are reachable but not covered

6

Reachable functions

37

Percentage of reachable functions covered

83.78%

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.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
tests/zip_fuzzer.c	1
build/amalgamation/miniz.c	31

Fuzzer: large_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	12	23.5%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	39	76.4%
All colors	51	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
0	268	1 : View List ['tdefl_compress_block']	0	268	tdefl_flush_block	call site: 00014	/src/miniz/build/amalgamation/miniz.c:1325
0	229	1 : View List ['mz_inflate']	4	237	test_large_inflate	call site: 00044	/src/miniz/tests/large_fuzzer.c:99
0	0	None	2	2	test_large_deflate	call site: 00031	/src/miniz/tests/large_fuzzer.c:54
0	0	None	2	2	test_large_deflate	call site: 00035	/src/miniz/tests/large_fuzzer.c:68
0	0	None	0	834	tdefl_compress	call site: 00010	/src/miniz/build/amalgamation/miniz.c:1944
0	0	None	0	371	tdefl_compress_normal	call site: 00012	/src/miniz/build/amalgamation/miniz.c:1834
0	0	None	0	255	tdefl_compress_block	call site: 00014	/src/miniz/build/amalgamation/miniz.c:1241
0	0	None	0	198	mz_inflate	call site: 00044	/src/miniz/build/amalgamation/miniz.c:467
0	0	None	0	198	mz_inflate	call site: 00047	/src/miniz/build/amalgamation/miniz.c:535
0	0	None	0	5	tdefl_compress	call site: 00028	/src/miniz/build/amalgamation/miniz.c:1970
0	0	None	0	3	tinfl_decompress	call site: 00045	/src/miniz/build/amalgamation/miniz.c:2491
0	0	None	0	3	tinfl_decompress	call site: 00046	/src/miniz/build/amalgamation/miniz.c:2605

Runtime coverage analysis

Covered functions

33

Functions that are reachable but not covered

4

Reachable functions

32

Percentage of reachable functions covered

87.5%

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.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
tests/large_fuzzer.c	3
build/amalgamation/miniz.c	26

Fuzzer: small_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	4	7.69%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	48	92.3%
All colors	52	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
2	2	1 : View List ['exit']	2	2	test_inflate	call site: 00049	/src/miniz/tests/small_fuzzer.c:95
0	268	1 : View List ['tdefl_compress_block']	0	268	tdefl_flush_block	call site: 00016	/src/miniz/build/amalgamation/miniz.c:1325
0	0	None	6	10	test_inflate	call site: 00042	/src/miniz/tests/small_fuzzer.c:87
0	0	None	0	371	tdefl_compress_normal	call site: 00014	/src/miniz/build/amalgamation/miniz.c:1832
0	0	None	0	371	tdefl_compress_normal	call site: 00014	/src/miniz/build/amalgamation/miniz.c:1859
0	0	None	0	198	mz_inflate	call site: 00042	/src/miniz/build/amalgamation/miniz.c:467
0	0	None	0	198	mz_inflate	call site: 00045	/src/miniz/build/amalgamation/miniz.c:535
0	0	None	0	5	tdefl_compress	call site: 00030	/src/miniz/build/amalgamation/miniz.c:1970
0	0	None	0	3	tinfl_decompress	call site: 00043	/src/miniz/build/amalgamation/miniz.c:2496
0	0	None	0	3	tinfl_decompress	call site: 00044	/src/miniz/build/amalgamation/miniz.c:2671
0	0	None	0	0	tdefl_compress	call site: 00012	/src/miniz/build/amalgamation/miniz.c:1915
0	0	None	0	0	tdefl_compress	call site: 00012	/src/miniz/build/amalgamation/miniz.c:1933

Runtime coverage analysis

Covered functions

36

Functions that are reachable but not covered

4

Reachable functions

35

Percentage of reachable functions covered

88.57%

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.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
tests/small_fuzzer.c	3
build/amalgamation/miniz.c	28

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.

Func name	Functions filename	Arg count	Args	Function depth	hitcount	instr count	bb count	cyclomatic complexity	Reachable functions	Incoming references	total cyclomatic complexity	Unreached complexity
mz_zip_add_mem_to_archive_file_in_place	/src/miniz/build/amalgamation/miniz.c	7	['N/A', 'N/A', 'N/A', 'size_t', 'N/A', 'short', 'int']	10	0	19	3	2	56	0	960	266
mz_zip_writer_add_from_zip_reader	/src/miniz/build/amalgamation/miniz.c	3	['N/A', 'N/A', 'int']	3	0	1501	207	82	10	0	178	107
mz_zip_writer_add_file	/src/miniz/build/amalgamation/miniz.c	6	['N/A', 'N/A', 'N/A', 'N/A', 'short', 'int']	9	0	75	12	6	40	0	681	93

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

Functions statically reachable by fuzzers

98 / 168

Cyclomatic complexity statically reachable by fuzzers

1760 / 2123

All functions overview

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

Func name	Functions filename	Args	Function call depth	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

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.

tests/checksum_fuzzer.c

Dictionary

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

tests/flush_fuzzer.c

Dictionary

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

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['mz_deflate', 'tdefl_compress_block', 'test_flush']

tests/uncompress_fuzzer.c

Dictionary

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

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['tinfl_decompress']

tests/compress_fuzzer.c

Dictionary

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

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['mz_deflate', 'tdefl_compress_block', 'tinfl_decompress']

tests/uncompress2_fuzzer.c

Dictionary

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

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['tinfl_decompress']

tests/zip_fuzzer.c

Dictionary

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

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['mz_zip_locate_file_binary_search', 'mz_zip_reader_file_stat', 'mz_zip_validate_file', 'mz_zip_reader_init_mem', 'tinfl_decompress']

tests/large_fuzzer.c

Dictionary

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

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['tdefl_flush_block', 'test_large_deflate', 'mz_deflate', 'tdefl_compress', 'tdefl_optimize_huffman_table', 'tdefl_compress_block', 'test_large_inflate', 'mz_inflate']

tests/small_fuzzer.c

Dictionary

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

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['test_inflate', 'tdefl_compress_block']

This section shows analysis of runtime coverage data.

For futher technical details on how this section is generated, please see the Glossary .

Complex functions with low coverage

Func name	Function total lines	Lines covered at runtime	percentage covered	Reached by fuzzers
mz_zip_reader_locate_file_v2	54	12	22.22%	['zip_fuzzer']
mz_zip_reader_end_internal	37	19	51.35%	['zip_fuzzer']

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/miniz/tests/checksum_fuzzer.c	['checksum_fuzzer']	['checksum_fuzzer']
/src/miniz/tests/flush_fuzzer.c	['flush_fuzzer']	['flush_fuzzer']
/src/miniz/tests/zip_fuzzer.c	['zip_fuzzer']	['zip_fuzzer']
/src/miniz/tests/uncompress2_fuzzer.c	['uncompress2_fuzzer']	['uncompress2_fuzzer']
/src/miniz/build/amalgamation/miniz.c	['checksum_fuzzer', 'flush_fuzzer', 'uncompress_fuzzer', 'compress_fuzzer', 'uncompress2_fuzzer', 'zip_fuzzer', 'large_fuzzer', 'small_fuzzer']	['checksum_fuzzer', 'flush_fuzzer', 'uncompress_fuzzer', 'compress_fuzzer', 'uncompress2_fuzzer', 'zip_fuzzer', 'large_fuzzer', 'small_fuzzer']
/src/miniz/tests/uncompress_fuzzer.c	['uncompress_fuzzer']	['uncompress_fuzzer']
/src/miniz/tests/compress_fuzzer.c	['compress_fuzzer']	['compress_fuzzer']
/src/miniz/tests/large_fuzzer.c	['large_fuzzer']	['large_fuzzer']
/usr/include/x86_64-linux-gnu/sys/stat.h	[]	[]
/src/miniz/tests/small_fuzzer.c	['small_fuzzer']	['small_fuzzer']

Directories in report

Directory
/usr/include/x86_64-linux-gnu/sys/
/src/miniz/build/amalgamation/
/src/miniz/tests/