High level conclusions

Fuzzer fuzzer_minigzip is blocked:

The runtime code coverage of fuzzer_minigzip covers 13.51% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzzer_example_dict is blocked:

The runtime code coverage of fuzzer_example_dict covers 20.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzzer_compress is blocked:

The runtime code coverage of fuzzer_compress covers 25.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzzer_example_large is blocked:

The runtime code coverage of fuzzer_example_large covers 20.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzzer_example_small is blocked:

The runtime code coverage of fuzzer_example_small covers 20.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzzer_example_flush is blocked:

The runtime code coverage of fuzzer_example_flush covers 21.42% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzzer_checksum is blocked:

The runtime code coverage of fuzzer_checksum covers 11.11% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzers reach 3.635% of cyclomatic complexity.

Fuzzers reach 3.278% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

26 / 793

Cyclomatic complexity statically reachable by fuzzers

67 / 1843

Runtime code coverage of functions

149 / 793

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	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: fuzzer_checksum

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	22	37.9%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	36	62.0%
All colors	58	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
22	1	LLVMFuzzerTestOneInput	call site: 00001	insert_knuth

Runtime coverage analysis

Covered functions

39

Functions that are reachable but not covered

8

Reachable functions

9

Percentage of reachable functions covered

11.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
test/fuzz/fuzzer_checksum.c	4
deflate.c	11
insert_string_p.h	6
zmemory.h	1

Fuzzer: fuzzer_example_flush

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	44	77.1%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	13	22.8%
All colors	57	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
17	37	LLVMFuzzerTestOneInput	call site: 00037	PREFIX
11	1	LLVMFuzzerTestOneInput	call site: 00001	insert_knuth
10	26	LLVMFuzzerTestOneInput	call site: 00026	PREFIX
5	18	insert_knuth	call site: 00018	UNLIKELY
1	14	insert_knuth	call site: 00014

Runtime coverage analysis

Covered functions

124

Functions that are reachable but not covered

11

Reachable functions

14

Percentage of reachable functions covered

21.43%

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
test/fuzz/fuzzer_example_flush.c	6
deflate.c	11
insert_string_p.h	6
zmemory.h	1
test/example.c	11

Fuzzer: fuzzer_example_small

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	42	76.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	13	23.6%
All colors	55	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
15	37	LLVMFuzzerTestOneInput	call site: 00037	PREFIX
11	1	LLVMFuzzerTestOneInput	call site: 00001	insert_knuth
10	26	LLVMFuzzerTestOneInput	call site: 00026	PREFIX
5	18	insert_knuth	call site: 00018	UNLIKELY
1	14	insert_knuth	call site: 00014

Runtime coverage analysis

Covered functions

100

Functions that are reachable but not covered

12

Reachable functions

15

Percentage of reachable functions covered

20.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
test/fuzz/fuzzer_example_small.c	6
deflate.c	11
insert_string_p.h	6
zmemory.h	1
test/example.c	12

Fuzzer: fuzzer_example_large

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	68	88.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	9	11.6%
All colors	77	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
47	16	update_hash_roll	call site: 00016	zng_deflateSetParams
11	4	LLVMFuzzerTestOneInput	call site: 00004	PREFIX
10	64	LLVMFuzzerTestOneInput	call site: 00064	PREFIX

Runtime coverage analysis

Covered functions

118

Functions that are reachable but not covered

12

Reachable functions

15

Percentage of reachable functions covered

20.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
test/fuzz/fuzzer_example_large.c	6
test/example.c	12
deflate.c	15
insert_string_p.h	6
zmemory.h	1

Fuzzer: fuzzer_compress

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	19	42.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	26	57.7%
All colors	45	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
11	1	LLVMFuzzerTestOneInput	call site: 00001	insert_knuth
5	18	insert_knuth	call site: 00018	UNLIKELY
2	29	check_compress_level	call site: 00029
1	14	insert_knuth	call site: 00014

Runtime coverage analysis

Covered functions

145

Functions that are reachable but not covered

12

Reachable functions

16

Percentage of reachable functions covered

25.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
test/fuzz/fuzzer_compress.c	12
deflate.c	11
insert_string_p.h	6
zmemory.h	1

Fuzzer: fuzzer_example_dict

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

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
20	38	LLVMFuzzerTestOneInput	call site: 00038	PREFIX
17	20	insert_knuth	call site: 00020	PREFIX
11	1	LLVMFuzzerTestOneInput	call site: 00001	PREFIX
1	13	update_hash_roll	call site: 00013	insert_knuth
1	16	insert_knuth	call site: 00016

Runtime coverage analysis

Covered functions

141

Functions that are reachable but not covered

12

Reachable functions

15

Percentage of reachable functions covered

20.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
test/fuzz/fuzzer_example_dict.c	4
test/example.c	13
deflate.c	11
insert_string_p.h	6
zmemory.h	1

Fuzzer: fuzzer_minigzip

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

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
11	46	file_compress	call site: 00046	gz_compress_mmap
9	21	file_compress	call site: 00021	PREFIX3
7	38	insert_knuth	call site: 00038	UNLIKELY
5	2	LLVMFuzzerTestOneInput	call site: 00002
2	14	file_compress	call site: 00014
2	18	file_compress	call site: 00018
2	60	gz_compress	call site: 00060
2	72	file_uncompress	call site: 00072
2	78	file_uncompress	call site: 00078
2	81	file_uncompress	call site: 00081
2	95	LLVMFuzzerTestOneInput	call site: 00095
2	100	LLVMFuzzerTestOneInput	call site: 00100

Runtime coverage analysis

Covered functions

171

Functions that are reachable but not covered

32

Reachable functions

37

Percentage of reachable functions covered

13.51%

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
test/fuzz/fuzzer_minigzip.c	28
test/example.c	4
deflate.c	11
insert_string_p.h	6
zmemory.h	1

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
zng_tr_flush_block	/src/zlib-ng/trees.c	4	['deflate_state*', 'unsigned char*', 'uint32_t', 'int']	6	0	41	8	9	54	0	116	114
gz_read	/src/zlib-ng/gzread.c	3	['gz_state*', 'void*', 'size_t']	9	0	46	13	17	27	0	89	83
inflate_bench::Dispatch	/src/zlib-ng/test/benchmarks/benchmark_inflate.cc	2	['benchmark::State', 'enum test_data_type']	6	0	5	2	1	28	0	76	71
block_state::deflate_medium	/src/zlib-ng/deflate_medium.c	2	['deflate_state*', 'int']	5	0	48	12	20	36	0	78	68
crc32_chorba_sse41	/src/zlib-ng/arch/x86/crc32_chorba_sse41.c	3	['uint32_t', 'uint8_t*', 'size_t']	3	0	13	5	5	44	1	71	66
adler32_avx512_vnni	/src/zlib-ng/arch/x86/adler32_avx512_vnni.c	3	['uint32_t', 'uint8_t*', 'size_t']	4	0	48	5	7	78	0	62	58
zng_inflate_table	/src/zlib-ng/inftrees.c	6	['codetype', 'uint16_t*', 'unsigned', 'code**', 'unsigned*', 'uint16_t*']	3	0	123	20	40	39	3	60	52
crc32_copy_impl	/src/zlib-ng/arch/arm/crc32_armv8_pmull_eor3.c	5	['uint32_t', 'uint8_t*', 'uint8_t*', 'size_t', 'int']	4	0	174	16	17	37	8	50	47
gz_write	/src/zlib-ng/gzwrite.c	3	['gz_state*', 'void*', 'size_t']	8	0	41	12	16	22	0	62	44
LONGEST_MATCH	/src/zlib-ng/match_tpl.h	2	['deflate_state*', 'uint32_t']	3	0	119	24	39	13	0	47	43

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

Functions statically reachable by fuzzers

213 / 793

Cyclomatic complexity statically reachable by fuzzers

713 / 1843

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	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

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.

test/fuzz/fuzzer_checksum.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=['LLVMFuzzerTestOneInput']

test/fuzz/fuzzer_example_flush.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=['LLVMFuzzerTestOneInput', 'insert_knuth']

test/fuzz/fuzzer_example_small.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=['LLVMFuzzerTestOneInput', 'insert_knuth']

test/fuzz/fuzzer_example_large.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=['update_hash_roll', 'LLVMFuzzerTestOneInput']

test/fuzz/fuzzer_compress.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=['LLVMFuzzerTestOneInput', 'insert_knuth', 'check_compress_level']

test/fuzz/fuzzer_example_dict.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=['LLVMFuzzerTestOneInput', 'insert_knuth', 'update_hash_roll']

test/fuzz/fuzzer_minigzip.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=['file_compress', 'insert_knuth', 'LLVMFuzzerTestOneInput', 'gz_compress', 'file_uncompress']

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
adler32_ssse3	85	41	48.23%	['fuzzer_example_large', 'fuzzer_compress', 'fuzzer_checksum', 'fuzzer_example_dict']
deflateHeaders	153	51	33.33%
zng_deflateBound	61	26	42.62%
gz_look	31	15	48.38%	['fuzzer_minigzip']
gz_write	46	25	54.34%	['fuzzer_minigzip']

New fuzzers

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

trees.c

Target file: /src/zlib-ng/trees.c
Target functions: zng_tr_flush_block

#include "ada_fuzz_header.h"

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

  /* target zng_tr_flush_block */
  UNKNOWN_TYPE unknown_0;
  UNKNOWN_TYPE unknown_1;
  UNKNOWN_TYPE unknown_2;
  int new_var3 = ada_safe_get_int();
  zng_tr_flush_block(unknown_0, unknown_1, unknown_2, new_var3);

  af_safe_gb_cleanup();
}

gzread.c

Target file: /src/zlib-ng/gzread.c
Target functions: gz_read

#include "ada_fuzz_header.h"

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

  /* target gz_read */
  UNKNOWN_TYPE unknown_4;
  UNKNOWN_TYPE unknown_5;
  UNKNOWN_TYPE unknown_6;
  gz_read(unknown_4, unknown_5, unknown_6);

  af_safe_gb_cleanup();
}

benchmark_inflate.cc

Target file: /src/zlib-ng/test/benchmarks/benchmark_inflate.cc
Target functions: inflate_bench::Dispatch

#include "ada_fuzz_header.h"

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

  /* target inflate_bench::Dispatch */
  UNKNOWN_TYPE unknown_7;
  UNKNOWN_TYPE unknown_8;
  inflate_bench::Dispatch(unknown_7, unknown_8);

  af_safe_gb_cleanup();
}

deflate_medium.c

Target file: /src/zlib-ng/deflate_medium.c
Target functions: block_state::deflate_medium

#include "ada_fuzz_header.h"

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

  /* target block_state::deflate_medium */
  UNKNOWN_TYPE unknown_9;
  int new_var10 = ada_safe_get_int();
  block_state::deflate_medium(unknown_9, new_var10);

  af_safe_gb_cleanup();
}

crc32_chorba_sse41.c

Target file: /src/zlib-ng/arch/x86/crc32_chorba_sse41.c
Target functions: crc32_chorba_sse41

#include "ada_fuzz_header.h"

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

  /* target crc32_chorba_sse41 */
  UNKNOWN_TYPE unknown_11;
  UNKNOWN_TYPE unknown_12;
  UNKNOWN_TYPE unknown_13;
  crc32_chorba_sse41(unknown_11, unknown_12, unknown_13);

  af_safe_gb_cleanup();
}

adler32_avx512_vnni.c

Target file: /src/zlib-ng/arch/x86/adler32_avx512_vnni.c
Target functions: adler32_avx512_vnni

#include "ada_fuzz_header.h"

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

  /* target adler32_avx512_vnni */
  UNKNOWN_TYPE unknown_14;
  UNKNOWN_TYPE unknown_15;
  UNKNOWN_TYPE unknown_16;
  adler32_avx512_vnni(unknown_14, unknown_15, unknown_16);

  af_safe_gb_cleanup();
}

inftrees.c

Target file: /src/zlib-ng/inftrees.c
Target functions: zng_inflate_table

#include "ada_fuzz_header.h"

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

  /* target zng_inflate_table */
  UNKNOWN_TYPE unknown_17;
  UNKNOWN_TYPE unknown_18;
  UNKNOWN_TYPE unknown_19;
  UNKNOWN_TYPE unknown_20;
  UNKNOWN_TYPE unknown_21;
  UNKNOWN_TYPE unknown_22;
  zng_inflate_table(unknown_17, unknown_18, unknown_19, unknown_20, unknown_21, unknown_22);

  af_safe_gb_cleanup();
}

crc32_armv8_pmull_eor3.c

Target file: /src/zlib-ng/arch/arm/crc32_armv8_pmull_eor3.c
Target functions: crc32_copy_impl

#include "ada_fuzz_header.h"

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

  /* target crc32_copy_impl */
  UNKNOWN_TYPE unknown_23;
  UNKNOWN_TYPE unknown_24;
  UNKNOWN_TYPE unknown_25;
  UNKNOWN_TYPE unknown_26;
  int new_var27 = ada_safe_get_int();
  crc32_copy_impl(unknown_23, unknown_24, unknown_25, unknown_26, new_var27);

  af_safe_gb_cleanup();
}

gzwrite.c

Target file: /src/zlib-ng/gzwrite.c
Target functions: gz_write

#include "ada_fuzz_header.h"

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

  /* target gz_write */
  UNKNOWN_TYPE unknown_28;
  UNKNOWN_TYPE unknown_29;
  UNKNOWN_TYPE unknown_30;
  gz_write(unknown_28, unknown_29, unknown_30);

  af_safe_gb_cleanup();
}

match_tpl.h

Target file: /src/zlib-ng/match_tpl.h
Target functions: LONGEST_MATCH

#include "ada_fuzz_header.h"

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

  /* target LONGEST_MATCH */
  UNKNOWN_TYPE unknown_31;
  UNKNOWN_TYPE unknown_32;
  LONGEST_MATCH(unknown_31, unknown_32);

  af_safe_gb_cleanup();
}

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/zlib-ng/arch/x86/adler32_avx512_vnni.c	[]	[]
/src/zlib-ng/test/benchmarks/benchmark_deflate.cc	[]	[]
/src/zlib-ng/test/test_deflate.cc	[]	[]
/src/zlib-ng/arch/x86/crc32_pclmulqdq_tpl.h	[]	[]
/src/zlib-ng/arch/power/adler32_power8.c	[]	[]
/src/zlib-ng/arch/generic/crc32_braid_c.c	[]	[]
/src/zlib-ng/trees_tbl.h	[]	[]
/src/zlib-ng/chunkset_tpl.h	[]	[]
/src/zlib-ng/arch/loongarch/lasxintrin_ext.h	[]	[]
/src/zlib-ng/arch/s390/dfltcc_common.h	[]	[]
/src/zlib-ng/test/test_raw.cc	[]	[]
/src/zlib-ng/test/benchmarks/benchmark_slidehash.cc	[]	[]
/src/zlib-ng/arch/power/compare256_power9.c	[]	[]
/src/zlib-ng/inflate_p.h	[]	[]
/src/zlib-ng/test/test_deflate_params.cc	[]	[]
/src/zlib-ng/adler32_p.h	[]	[]
/src/zlib-ng/arch/generic/adler32_c.c	[]	[]
/src/zlib-ng/test/fuzz/fuzzer_example_dict.c	['fuzzer_example_dict']	['fuzzer_example_dict']
/src/zlib-ng/arch/x86/x86_intrins.h	[]	[]
/src/zlib-ng/arch/power/slide_ppc_tpl.h	[]	[]
/src/zlib-ng/arch/riscv/chunkset_rvv.c	[]	[]
/src/zlib-ng/deflate_stored.c	[]	[]
/src/zlib-ng/arch/loongarch/slide_hash_lasx.c	[]	[]
/src/zlib-ng/functable.c	[]	[]
/src/zlib-ng/arch/generic/slide_hash_c.c	[]	[]
/src/zlib-ng/test/test_data_p.h	[]	[]
/src/zlib-ng/crc32.c	[]	[]
/src/zlib-ng/arch/x86/crc32_chorba_sse41.c	[]	[]
/src/zlib-ng/arch/x86/compare256_sse2.c	[]	[]
/src/zlib-ng/deflate_p.h	[]	[]
/src/zlib-ng/arch/arm/adler32_neon.c	[]	[]
/src/zlib-ng/test/fuzz/fuzzer_example_flush.c	['fuzzer_example_flush']	['fuzzer_example_flush']
/src/zlib-ng/arch/power/chunkset_power8.c	[]	[]
/src/zlib-ng/arch/x86/adler32_avx512.c	[]	[]
/src/zlib-ng/arch/x86/crc32_vpclmulqdq_avx512.c	[]	[]
/src/zlib-ng/deflate_medium.c	[]	[]
/src/zlib-ng/test/benchmarks/benchmark_png_decode.cc	[]	[]
/src/zlib-ng/test/benchmarks/benchmark_png_shared.h	[]	[]
/src/zlib-ng/arch/power/power_intrins.h	[]	[]
/src/zlib-ng/gzread.c	[]	[]
/src/zlib-ng/deflate_rle.c	[]	[]
/src/zlib-ng/utils/makefixed.c	[]	[]
/src/zlib-ng/test/test_adler32.cc	[]	[]
/src/zlib-ng/insert_string.c	[]	[]
/src/zlib-ng/arch/x86/chunkset_avx512.c	[]	[]
/src/zlib-ng/arch/s390/vx_intrins.h	[]	[]
/src/zlib-ng/arch/arm/slide_hash_armv6.c	[]	[]
/src/zlib-ng/arch/arm/chunkset_neon.c	[]	[]
/src/zlib-ng/test/benchmarks/benchmark_main.cc	[]	[]
/src/zlib-ng/arch/riscv/crc32_zbc.c	[]	[]
/src/zlib-ng/deflate.h	[]	[]
/src/zlib-ng/test/benchmarks/benchmark_data_types.cc	[]	[]
/src/zlib-ng/arch/x86/adler32_avx512_p.h	[]	[]
/src/zlib-ng/trees.c	[]	[]
/src/zlib-ng/zutil.h	[]	[]
/src/zlib-ng/crc32_braid_comb.c	[]	[]
/src/zlib-ng/test/test_chunked.cc	[]	[]
/src/zlib-ng/arch/arm/crc32_armv8_pmull_eor3.c	[]	[]
/src/zlib-ng/test/test_compare256_rle.cc	[]	[]
/src/zlib-ng/zendian.h	[]	[]
/src/zlib-ng/test/benchmarks/benchmark_inflate_chunked.cc	[]	[]
/src/zlib-ng/arch/x86/slide_hash_avx2.c	[]	[]
/src/zlib-ng/match_tpl.h	[]	[]
/src/zlib-ng/zutil_p.h	[]	[]
/src/zlib-ng/inftrees.c	[]	[]
/src/zlib-ng/arch/x86/crc32_vpclmulqdq_avx2.c	[]	[]
/src/zlib-ng/inflate.c	[]	[]
/src/zlib-ng/test/test_deflate_concurrency.cc	[]	[]
/src/zlib-ng/arch/riscv/riscv_features.c	[]	[]
/src/zlib-ng/test/benchmarks/benchmark_chunkmemset.cc	[]	[]
/src/zlib-ng/functable.h	[]	[]
/src/zlib-ng/arch/riscv/compare256_rvv.c	[]	[]
/src/zlib-ng/arch/x86/crc32_chorba_sse2.c	[]	[]
/src/zlib-ng/arch/loongarch/loongarch_features.c	[]	[]
/src/zlib-ng/utils/minideflate.c	[]	[]
/src/zlib-ng/test/benchmarks/benchmark_inflate.cc	[]	[]
/src/zlib-ng/arch/arm/arm_features.c	[]	[]
/src/zlib-ng/test/fuzz/fuzzer_compress.c	['fuzzer_compress']	['fuzzer_compress']
/src/zlib-ng/arch/power/crc32_power8.c	[]	[]
/src/zlib-ng/test/fuzz/fuzzer_checksum.c	['fuzzer_checksum']	['fuzzer_checksum']
/src/zlib-ng/gzlib.c	[]	[]
/src/zlib-ng/test/switchlevels.c	[]	[]
/src/zlib-ng/test/benchmarks/benchmark_png_decode_small.cc	[]	[]
/src/zlib-ng/test/benchmarks/benchmark_adler32.cc	[]	[]
/src/zlib-ng/arch/s390/slide_hash_vx.c	[]	[]
/src/zlib-ng/arch/arm/slide_hash_neon.c	[]	[]
/src/zlib-ng/arch/loongarch/crc32_la.c	[]	[]
/src/zlib-ng/test/benchmarks/benchmark_uncompress.cc	[]	[]
/src/zlib-ng/test/benchmarks/benchmark_crc32.cc	[]	[]
/src/zlib-ng/adler32.c	[]	[]
/src/zlib-ng/test/test_compress_bound.cc	[]	[]
/src/zlib-ng/zsanitizer.h	[]	[]
/src/zlib-ng/trees_emit.h	[]	[]
/src/zlib-ng/crc32_chorba_p.h	[]	[]
/src/zlib-ng/arch/riscv/adler32_rvv.c	[]	[]
/src/zlib-ng/arch/x86/slide_hash_sse2.c	[]	[]
/src/zlib-ng/arch/power/adler32_vmx.c	[]	[]
/src/zlib-ng/gzguts.h	[]	[]
/src/zlib-ng/fallback_builtins.h	[]	[]
/src/zlib-ng/arch/shared/crc32_hw_copy_impl_tpl.h	[]	[]
/src/zlib-ng/arch/riscv/slide_hash_rvv.c	[]	[]
/src/zlib-ng/utils/minigzip.c	[]	[]
/src/zlib-ng/test/benchmarks/benchmark_corpora.cc	[]	[]
/src/zlib-ng/arch/s390/crc32_vx.c	[]	[]
/src/zlib-ng/deflate.c	['fuzzer_checksum', 'fuzzer_example_flush', 'fuzzer_example_small', 'fuzzer_example_large', 'fuzzer_compress', 'fuzzer_example_dict', 'fuzzer_minigzip']	['fuzzer_example_flush', 'fuzzer_example_small', 'fuzzer_example_large', 'fuzzer_compress', 'fuzzer_example_dict', 'fuzzer_minigzip']
/src/zlib-ng/arch/loongarch/adler32_lasx.c	[]	[]
/src/zlib-ng/deflate_quick.c	[]	[]
/src/zlib-ng/test/test_inflate_back.cc	[]	[]
/src/zlib-ng/arch/arm/crc32_armv8.c	[]	[]
/src/zlib-ng/arch/x86/adler32_avx2.c	[]	[]
/src/zlib-ng/arch/arm/neon_intrins.h	[]	[]
/src/zlib-ng/arch/loongarch/chunkset_lasx.c	[]	[]
/src/zlib-ng/test/benchmarks/benchmark_adler32_copy.cc	[]	[]
/src/zlib-ng/deflate_huff.c	[]	[]
/src/zlib-ng/zutil.c	[]	[]
/src/zlib-ng/cpu_features.c	[]	[]
/src/zlib-ng/crc32_braid_comb_p.h	[]	[]
/src/zlib-ng/infback.c	[]	[]
/src/zlib-ng/zarch.h	[]	[]
/src/zlib-ng/test/benchmarks/benchmark_compare256_rle.cc	[]	[]
/src/zlib-ng/test/fuzz/fuzzer_minigzip.c	['fuzzer_minigzip']	['fuzzer_minigzip']
/src/zlib-ng/deflate_fast.c	[]	[]
/src/zlib-ng/arch/x86/compare256_avx2.c	[]	[]
/src/zlib-ng/arch/x86/adler32_ssse3.c	[]	[]
/src/zlib-ng/test/test_compare256.cc	[]	[]
/src/zlib-ng/arch/s390/dfltcc_inflate.h	[]	[]
/src/zlib-ng/arch/power/power_features.c	[]	[]
/src/zlib-ng/arch/generic/crc32_chorba_c.c	[]	[]
/src/zlib-ng/arch/s390/dfltcc_deflate.h	[]	[]
/src/zlib-ng/test/test_deflate_deterministic.cc	[]	[]
/src/zlib-ng/arch/x86/adler32_sse42.c	[]	[]
/src/zlib-ng/crc32_braid_p.h	[]	[]
/src/zlib-ng/test/test_crc32_copy.cc	[]	[]
/src/zlib-ng/test/benchmarks/benchmark_png_encode.cc	[]	[]
/src/zlib-ng/test/test_crc32.cc	[]	[]
/src/zlib-ng/compare256_rle.h	[]	[]
/src/zlib-ng/arch/x86/crc32_pclmulqdq.c	[]	[]
/src/zlib-ng/arch/arm/adler32_neon_dotprod.c	[]	[]
/src/zlib-ng/zmemory.h	['fuzzer_checksum', 'fuzzer_example_flush', 'fuzzer_example_small', 'fuzzer_example_large', 'fuzzer_compress', 'fuzzer_example_dict', 'fuzzer_minigzip']	['fuzzer_example_flush', 'fuzzer_example_small', 'fuzzer_example_large', 'fuzzer_compress', 'fuzzer_example_dict', 'fuzzer_minigzip']
/src/zlib-ng/test/benchmarks/benchmark_compare256.cc	[]	[]
/src/zlib-ng/zbuild.h	[]	[]
/src/zlib-ng/arch/arm/crc32_armv8_p.h	[]	[]
/src/zlib-ng/arch/x86/x86_features.c	[]	[]
/src/zlib-ng/test/benchmarks/benchmark_compress.cc	[]	[]
/src/zlib-ng/arch/arm/compare256_neon.c	[]	[]
/src/zlib-ng/test/benchmarks/benchmark_crc32_copy.cc	[]	[]
/src/zlib-ng/test/benchmarks/benchmark_insert_string.cc	[]	[]
/src/zlib-ng/arch/loongarch/adler32_lsx.c	[]	[]
/src/zlib-ng/utils/makecrct.c	[]	[]
/src/zlib-ng/test/fuzz/fuzzer_example_small.c	['fuzzer_example_small']	['fuzzer_example_small']
/src/zlib-ng/test/test_adler32_copy.cc	[]	[]
/src/zlib-ng/crc32_p.h	[]	[]
/src/zlib-ng/arch/s390/dfltcc_deflate.c	[]	[]
/src/zlib-ng/arch/loongarch/compare256_lsx.c	[]	[]
/src/zlib-ng/arch/x86/adler32_avx2_vnni.c	[]	[]
/src/zlib-ng/arch/loongarch/slide_hash_lsx.c	[]	[]
/src/zlib-ng/test/hash_test_strings_p.h	[]	[]
/src/zlib-ng/gzwrite.c	[]	[]
/src/zlib-ng/arch/generic/compare256_c.c	[]	[]
/src/zlib-ng/arch/shared/crc32_hw_common_tpl.h	[]	[]
/src/zlib-ng/test/example.c	['fuzzer_example_flush', 'fuzzer_example_small', 'fuzzer_example_large', 'fuzzer_example_dict', 'fuzzer_minigzip']	[]
/src/zlib-ng/arch/arm/adler32_neon_tpl.h	[]	[]
/src/zlib-ng/utils/maketrees.c	[]	[]
/src/zlib-ng/arch/arm/acle_intrins.h	[]	[]
/src/zlib-ng/test/test_deflate_bound.cc	[]	[]
/src/zlib-ng/arch/x86/compare256_avx512.c	[]	[]
/src/zlib-ng/arch/s390/dfltcc_detail.h	[]	[]
/src/zlib-ng/arch/s390/dfltcc_inflate.c	[]	[]
/src/zlib-ng/test/infcover.c	[]	[]
/src/zlib-ng/test/fuzz/fuzzer_example_large.c	['fuzzer_example_large']	['fuzzer_example_large']
/src/zlib-ng/arch/loongarch/compare256_lasx.c	[]	[]
/src/zlib-ng/deflate_slow.c	[]	[]
/src/zlib-ng/arch/loongarch/lsxintrin_ext.h	[]	[]
/src/zlib-ng/arch/s390/s390_features.c	[]	[]
/src/zlib-ng/insert_string_p.h	['fuzzer_checksum', 'fuzzer_example_flush', 'fuzzer_example_small', 'fuzzer_example_large', 'fuzzer_compress', 'fuzzer_example_dict', 'fuzzer_minigzip']	['fuzzer_example_flush', 'fuzzer_example_small', 'fuzzer_example_large', 'fuzzer_compress', 'fuzzer_example_dict', 'fuzzer_minigzip']

Directories in report

Directory
/src/zlib-ng/test/
/src/zlib-ng/arch/power/
/src/zlib-ng/arch/x86/
/src/zlib-ng/test/fuzz/
/src/zlib-ng/arch/loongarch/
/src/zlib-ng/arch/shared/
/src/zlib-ng/arch/riscv/
/src/zlib-ng/test/benchmarks/
/src/zlib-ng/
/src/zlib-ng/utils/
/src/zlib-ng/arch/generic/
/src/zlib-ng/arch/arm/
/src/zlib-ng/arch/s390/

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

Target sink	Callsite location	Reached by fuzzer	Covered by Fuzzers