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

Fuzzer details

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 30 31.9%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 64 68.0%
All colors 94 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 6 1 :

['avahi_free']

0 6 avahi_realloc call site: 00000 /src/avahi/avahi-common/malloc.c:148
0 0 None 6 23 avahi_unescape_label call site: 00044 /src/avahi/avahi-common/domain.c:81
0 0 None 2 21 avahi_strdup call site: 00049 /src/avahi/avahi-common/malloc.c:164
0 0 None 0 163 avahi_dns_packet_consume_key call site: 00025 /src/avahi/avahi-core/dns.c:673
0 0 None 0 100 avahi_key_new call site: 00028 /src/avahi/avahi-core/rr.c:47
0 0 None 0 36 avahi_is_valid_domain_name call site: 00060 /src/avahi/avahi-common/domain.c:379
0 0 None 0 31 avahi_strdup_vprintf call site: 00078 /src/avahi/avahi-common/malloc.c:206
0 0 None 0 31 avahi_strdup_vprintf call site: 00079 /src/avahi/avahi-common/malloc.c:221
0 0 None 0 31 avahi_strdup_vprintf call site: 00079 /src/avahi/avahi-common/malloc.c:226
0 0 None 0 19 avahi_dns_packet_new call site: 00003 /src/avahi/avahi-core/dns.c:43
0 0 None 0 19 avahi_dns_packet_new call site: 00003 /src/avahi/avahi-core/dns.c:45
0 0 None 0 0 avahi_unescape_label call site: 00042 /src/avahi/avahi-common/domain.c:52

Runtime coverage analysis

Covered functions
32
Functions that are reachable but not covered
12
Reachable functions
44
Percentage of reachable functions covered
72.73%
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 7
avahi-common/domain.c 5
avahi-core/rr.c 6
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 42 22.7%
gold [1:9] 4 2.16%
yellow [10:29] 4 2.16%
greenyellow [30:49] 4 2.16%
lawngreen 50+ 131 70.8%
All colors 185 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 6 1 :

['avahi_free']

0 6 avahi_realloc call site: 00000 /src/avahi/avahi-common/malloc.c:148
0 0 None 6 23 avahi_unescape_label call site: 00049 /src/avahi/avahi-common/domain.c:81
0 0 None 4 98 avahi_record_is_valid call site: 00117 /src/avahi/avahi-core/rr.c:670
0 0 None 2 21 avahi_strdup call site: 00054 /src/avahi/avahi-common/malloc.c:164
0 0 None 0 316 avahi_dns_packet_consume_record call site: 00029 /src/avahi/avahi-core/dns.c:639
0 0 None 0 100 avahi_key_new call site: 00033 /src/avahi/avahi-core/rr.c:47
0 0 None 0 36 avahi_string_list_parse call site: 00097 /src/avahi/avahi-common/strlst.c:89
0 0 None 0 31 avahi_strdup_vprintf call site: 00166 /src/avahi/avahi-common/malloc.c:206
0 0 None 0 31 avahi_strdup_vprintf call site: 00167 /src/avahi/avahi-common/malloc.c:221
0 0 None 0 31 avahi_strdup_vprintf call site: 00167 /src/avahi/avahi-common/malloc.c:226
0 0 None 0 19 avahi_dns_packet_new call site: 00003 /src/avahi/avahi-core/dns.c:43
0 0 None 0 19 avahi_dns_packet_new call site: 00003 /src/avahi/avahi-core/dns.c:45

Runtime coverage analysis

Covered functions
51
Functions that are reachable but not covered
15
Reachable functions
66
Percentage of reachable functions covered
77.27%
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 12
avahi-common/malloc.c 8
avahi-common/domain.c 5
avahi-core/rr.c 12
avahi-core/../avahi-common/malloc.h 1
avahi-common/utf8.c 1
avahi-common/strlst.c 6
avahi-common/./malloc.h 1
avahi-core/hashmap.c 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/avahi/fuzz/fuzz-consume-key.c ['fuzz-consume-key'] ['fuzz-consume-key']
/src/avahi/avahi-core/hashmap.c ['fuzz-consume-key', 'fuzz-consume-record'] []
/src/avahi/avahi-core/../avahi-common/malloc.h ['fuzz-consume-key', 'fuzz-consume-record'] []
/src/avahi/avahi-common/address.c [] []
/src/avahi/avahi-common/domain.c ['fuzz-consume-key', 'fuzz-consume-record'] ['fuzz-consume-key', 'fuzz-consume-record']
/src/avahi/avahi-core/rr.c ['fuzz-consume-key', 'fuzz-consume-record'] ['fuzz-consume-key', 'fuzz-consume-record']
/src/avahi/avahi-core/domain-util.c [] []
/src/avahi/avahi-common/strlst.c ['fuzz-consume-record'] ['fuzz-consume-record']
/src/avahi/avahi-core/util.c [] []
/src/avahi/avahi-common/malloc.c ['fuzz-consume-key', 'fuzz-consume-record'] ['fuzz-consume-key', 'fuzz-consume-record']
/src/avahi/fuzz/fuzz-consume-record.c ['fuzz-consume-record'] ['fuzz-consume-record']
/src/avahi/avahi-core/dns.c ['fuzz-consume-key', 'fuzz-consume-record'] ['fuzz-consume-key', 'fuzz-consume-record']
/src/avahi/avahi-core/addr-util.c [] []
/src/avahi/avahi-common/utf8.c ['fuzz-consume-key', 'fuzz-consume-record'] ['fuzz-consume-key', 'fuzz-consume-record']
/src/avahi/avahi-core/log.c ['fuzz-consume-key', 'fuzz-consume-record'] ['fuzz-consume-key', 'fuzz-consume-record']
/src/avahi/avahi-common/./malloc.h ['fuzz-consume-record'] []

Directories in report

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