High level conclusions

Fuzzers reach 82.17% of cyclomatic complexity.

Fuzzers reach 71.97% of all functions.

Fuzzer fuzz-consume-record is blocked:

The runtime code coverage of fuzz-consume-record covers 0.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 fuzz-consume-key is blocked:

The runtime code coverage of fuzz-consume-key covers 0.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 fuzz-packet is blocked:

The runtime code coverage of fuzz-packet covers 0.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 fuzz-domain is blocked:

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

Reachability and coverage overview

Functions statically reachable by fuzzers

131 / 182

Cyclomatic complexity statically reachable by fuzzers

839 / 1021

Runtime code coverage of functions

29 / 182

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: fuzz-domain

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	170	100.%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	0	0.0%
All colors	170	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
169	0	EP	call site: 00000	avahi_alternative_host_name

Runtime coverage analysis

Covered functions

0

Functions that are reachable but not covered

44

Reachable functions

44

Percentage of reachable functions covered

0.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
fuzz/fuzz-domain.c	1
avahi-common/malloc.c	10
avahi-common/domain.c	13
avahi-common/utf8.c	1
avahi-common/address.c	2
avahi-common/alternative.c	3
avahi-common/./malloc.h	1

Fuzzer: fuzz-ini-file-parser

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	9	12.0%
gold	[1:9]	2	2.66%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	4	5.33%
lawngreen	50+	60	80.0%
All colors	75	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
5	19	avahi_malloc	call site: 00019	oom
3	9	avahi_ini_file_load	call site: 00009	avahi_log_error
1	14	avahi_log_ap	call site: 00014	fprintf

Runtime coverage analysis

Covered functions

16

Functions that are reachable but not covered

20

Reachable functions

36

Percentage of reachable functions covered

44.44%

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-ini-file-parser.c	2
avahi-core/log.c	4
avahi-daemon/ini-file-parser.c	4
./avahi-common/malloc.h	1
avahi-common/malloc.c	6
avahi-common/./malloc.h	1

Fuzzer: fuzz-strlst

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	16.6%
gold	[1:9]	1	1.38%
yellow	[10:29]	8	11.1%
greenyellow	[30:49]	1	1.38%
lawngreen	50+	50	69.4%
All colors	72	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
5	8	avahi_malloc	call site: 00008	oom
5	37	avahi_string_list_get_pair	call site: 00037	avahi_strndup
1	45	avahi_memdup	call site: 00045	avahi_free
1	63	avahi_string_list_copy	call site: 00063	avahi_string_list_free

Runtime coverage analysis

Covered functions

19

Functions that are reachable but not covered

12

Reachable functions

31

Percentage of reachable functions covered

61.29%

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-strlst.c	1
avahi-common/strlst.c	12
avahi-common/malloc.c	7
avahi-common/./malloc.h	1
avahi-common/utf8.c	1

Fuzzer: fuzz-packet

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	389	100.%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	0	0.0%
All colors	389	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
388	0	EP	call site: 00000	copy_rrs

Runtime coverage analysis

Covered functions

0

Functions that are reachable but not covered

111

Reachable functions

111

Percentage of reachable functions covered

0.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
fuzz/fuzz-packet.c	4
avahi-core/log.c	3
avahi-core/dns.c	28
avahi-common/malloc.c	12
avahi-common/domain.c	13
avahi-core/rr.c	12
avahi-core/../avahi-common/malloc.h	2
avahi-common/utf8.c	1
avahi-core/domain-util.c	1
avahi-core/hashmap.c	10
avahi-common/strlst.c	7
avahi-common/./malloc.h	1

Fuzzer: fuzz-consume-key

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	132	100.%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	0	0.0%
All colors	132	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
131	0	EP	call site: 00000	avahi_dns_packet_consume_key

Runtime coverage analysis

Covered functions

0

Functions that are reachable but not covered

52

Reachable functions

52

Percentage of reachable functions covered

0.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
fuzz/fuzz-consume-key.c	2
avahi-core/log.c	3
avahi-core/dns.c	6
avahi-common/malloc.c	9
avahi-common/domain.c	7
avahi-core/rr.c	10
avahi-core/../avahi-common/malloc.h	1
avahi-common/utf8.c	1
avahi-core/hashmap.c	2

Fuzzer: fuzz-consume-record

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	408	100.%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	0	0.0%
All colors	408	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
407	0	EP	call site: 00000	avahi_dns_packet_consume_record

Runtime coverage analysis

Covered functions

0

Functions that are reachable but not covered

112

Reachable functions

112

Percentage of reachable functions covered

0.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
fuzz/fuzz-consume-record.c	2
avahi-core/log.c	3
avahi-core/dns.c	24
avahi-common/malloc.c	12
avahi-common/domain.c	6
avahi-core/rr.c	24
avahi-core/../avahi-common/malloc.h	2
avahi-common/utf8.c	1
avahi-common/strlst.c	9
avahi-core/addr-util.c	1
avahi-common/./malloc.h	1
avahi-core/hashmap.c	10
avahi-core/domain-util.c	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
avahi_get_host_name	/src/avahi/avahi-core/domain-util.c	2	['N/A', 'size_t']	3	0	197	41	12	24	1	75	44

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

Functions statically reachable by fuzzers

138 / 182

Cyclomatic complexity statically reachable by fuzzers

877 / 1021

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.

fuzz/fuzz-domain.c

Dictionary

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

fuzz/fuzz-ini-file-parser.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=['avahi_malloc', 'avahi_ini_file_load', 'avahi_log_ap']

fuzz/fuzz-strlst.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=['avahi_malloc', 'avahi_string_list_get_pair', 'avahi_memdup', 'avahi_string_list_copy']

fuzz/fuzz-packet.c

Dictionary

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

fuzz/fuzz-consume-key.c

Dictionary

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

fuzz/fuzz-consume-record.c

Dictionary

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

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
avahi_utf8_valid	52	11	21.15%	['fuzz-strlst', 'fuzz-consume-key', 'fuzz-domain', 'fuzz-packet', 'fuzz-consume-record']

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/avahi/fuzz/fuzz-consume-record.c	['fuzz-consume-record']	[]
/src/avahi/avahi-common/strlst.c	['fuzz-strlst', 'fuzz-packet', 'fuzz-consume-record']	['fuzz-strlst']
/src/avahi/fuzz/fuzz-domain.c	['fuzz-domain']	[]
/src/avahi/avahi-common/alternative.c	['fuzz-domain']	[]
/src/avahi/avahi-core/hashmap.c	['fuzz-packet', 'fuzz-consume-key', 'fuzz-consume-record']	[]
/src/avahi/avahi-core/domain-util.c	['fuzz-packet', 'fuzz-consume-record']	[]
/src/avahi/avahi-common/domain.c	['fuzz-domain', 'fuzz-packet', 'fuzz-consume-key', 'fuzz-consume-record']	[]
/src/avahi/avahi-daemon/ini-file-parser.c	['fuzz-ini-file-parser']	['fuzz-ini-file-parser']
/src/avahi/avahi-common/utf8.c	['fuzz-domain', 'fuzz-strlst', 'fuzz-packet', 'fuzz-consume-key', 'fuzz-consume-record']	['fuzz-strlst']
/src/avahi/avahi-common/address.c	['fuzz-domain']	[]
/src/avahi/avahi-core/dns.c	['fuzz-packet', 'fuzz-consume-key', 'fuzz-consume-record']	[]
/src/avahi/fuzz/fuzz-consume-key.c	['fuzz-consume-key']	[]
/src/avahi/avahi-common/malloc.c	['fuzz-domain', 'fuzz-ini-file-parser', 'fuzz-strlst', 'fuzz-packet', 'fuzz-consume-key', 'fuzz-consume-record']	['fuzz-ini-file-parser', 'fuzz-strlst']
/src/avahi/fuzz/fuzz-strlst.c	['fuzz-strlst']	['fuzz-strlst']
/src/avahi/avahi-core/log.c	['fuzz-ini-file-parser', 'fuzz-packet', 'fuzz-consume-key', 'fuzz-consume-record']	['fuzz-ini-file-parser']
/src/avahi/avahi-core/rr.c	['fuzz-packet', 'fuzz-consume-key', 'fuzz-consume-record']	[]
/src/avahi/fuzz/fuzz-packet.c	['fuzz-packet']	[]
/src/avahi/avahi-core/util.c	[]	[]
/src/avahi/avahi-common/./malloc.h	['fuzz-domain', 'fuzz-ini-file-parser', 'fuzz-strlst', 'fuzz-packet', 'fuzz-consume-record']	[]
/src/avahi/avahi-core/addr-util.c	['fuzz-consume-record']	[]
/src/avahi/fuzz/fuzz-ini-file-parser.c	['fuzz-ini-file-parser']	['fuzz-ini-file-parser']
/src/avahi/avahi-core/../avahi-common/malloc.h	['fuzz-packet', 'fuzz-consume-key', 'fuzz-consume-record']	[]

Directories in report

Directory
/src/avahi/avahi-core/../avahi-common/
/src/avahi/avahi-daemon/
/src/avahi/avahi-core/
/src/avahi/avahi-common/./
/src/avahi/avahi-common/
/src/avahi/fuzz/