High level conclusions

Fuzzers reach 57.94% of cyclomatic complexity.

Fuzzers reach 54.0% of all functions.

Fuzzer fuzz_filter is blocked:

The runtime code coverage of fuzz_filter 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_pcap is blocked:

The runtime code coverage of fuzz_pcap covers 28.57% 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

324/600

Cyclomatic complexity statically reachable by fuzzers

2116/3652

Functions covered at runtime

261

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

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	28	41.7%
gold	[1:9]	3	4.47%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	36	53.7%
All colors	67	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
15	15	2 : View List ['__errno_location', 'pcap_fmt_errmsg_for_errno']	15	15	pcap_alloc_pcap_t	call site	/src/libpcap/pcap.c:2454
15	15	2 : View List ['__errno_location', 'pcap_fmt_errmsg_for_errno']	15	15	pcap_fopen_offline_with_tstamp_precision	call site	/src/libpcap/savefile.c:513
15	15	2 : View List ['__errno_location', 'pcap_fmt_errmsg_for_errno']	15	15	pcap_check_header	call site	/src/libpcap/sf-pcap.c:191
15	15	2 : View List ['__errno_location', 'pcap_fmt_errmsg_for_errno']	15	15	pcap_next_packet	call site	/src/libpcap/sf-pcap.c:467
15	15	2 : View List ['__errno_location', 'pcap_fmt_errmsg_for_errno']	15	15	pcap_next_packet	call site	/src/libpcap/sf-pcap.c:621
15	15	2 : View List ['__errno_location', 'pcap_fmt_errmsg_for_errno']	15	15	pcap_next_packet	call site	/src/libpcap/sf-pcap.c:652
15	15	2 : View List ['__errno_location', 'pcap_fmt_errmsg_for_errno']	15	15	pcap_next_packet	call site	/src/libpcap/sf-pcap.c:704
15	15	2 : View List ['__errno_location', 'pcap_fmt_errmsg_for_errno']	15	15	pcap_ng_check_header	call site	/src/libpcap/sf-pcapng.c:822
15	15	2 : View List ['__errno_location', 'pcap_fmt_errmsg_for_errno']	15	15	pcap_ng_check_header	call site	/src/libpcap/sf-pcapng.c:837
15	15	2 : View List ['__errno_location', 'pcap_fmt_errmsg_for_errno']	15	15	read_bytes	call site	/src/libpcap/sf-pcapng.c:265
2	2	1 : View List ['__errno_location']	2	2	bufferToFile	call site	/src/libpcap/build/../testprogs/fuzz/fuzz_pcap.c:21
0	0	None	38	134	pcap_next_packet	call site	/src/libpcap/sf-pcap.c:612

Runtime coverage analysis

Covered functions

41

Functions that are reachable but not covered

30

Reachable functions

42

Percentage of reachable functions covered

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
build/../testprogs/fuzz/fuzz_pcap.c	2
savefile.c	10
fmtutils.c	2
bpf_filter.c	2
extract.h	2
missing/strlcpy.c	1
pcap.c	4

Fuzzer: fuzz_filter

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	2071	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	2071	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
2070	0	EP	call site	pcap_compile

Runtime coverage analysis

Covered functions

0

Functions that are reachable but not covered

299

Reachable functions

299

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
build/../testprogs/fuzz/fuzz_filter.c	1
pcap.c	20
gencode.c	155
build/scanner.c	24
fmtutils.c	2
build/grammar.c	2
missing/strlcpy.c	1
scanner.l	1
nametoaddr.c	13
extract.h	2
build/grammar.y	4
optimize.c	47

Fuzzer: fuzz_both

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	614	29.1%
gold	[1:9]	254	12.0%
yellow	[10:29]	53	2.51%
greenyellow	[30:49]	49	2.32%
lawngreen	50+	1134	53.8%
All colors	2104	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
337	337	1 : View List ['gen_vlan_bpf_extensions']	337	337	gen_vlan	call site	/src/libpcap/gencode.c:8970
85	85	8 : View List ['ferror', 'getc', 'pcap_restart', 'yy_fatal_error', 'pcap_realloc', 'fread', '__errno_location', 'clearerr']	85	85	yy_get_next_buffer	call site	/src/libpcap/build/scanner.c:4629
25	25	1 : View List ['gen_geneve_ll_check']	25	25	gen_prevlinkhdr_check	call site	/src/libpcap/gencode.c:3149
15	15	2 : View List ['__errno_location', 'pcap_fmt_errmsg_for_errno']	19	2033	pcap_compile	call site	/src/libpcap/gencode.c:788
15	15	2 : View List ['__errno_location', 'pcap_fmt_errmsg_for_errno']	15	15	pcap_alloc_pcap_t	call site	/src/libpcap/pcap.c:2454
15	15	2 : View List ['__errno_location', 'pcap_fmt_errmsg_for_errno']	15	15	pcap_fopen_offline_with_tstamp_precision	call site	/src/libpcap/savefile.c:513
15	15	2 : View List ['__errno_location', 'pcap_fmt_errmsg_for_errno']	15	15	pcap_check_header	call site	/src/libpcap/sf-pcap.c:191
15	15	2 : View List ['__errno_location', 'pcap_fmt_errmsg_for_errno']	15	15	pcap_next_packet	call site	/src/libpcap/sf-pcap.c:467
15	15	2 : View List ['__errno_location', 'pcap_fmt_errmsg_for_errno']	15	15	pcap_next_packet	call site	/src/libpcap/sf-pcap.c:621
15	15	2 : View List ['__errno_location', 'pcap_fmt_errmsg_for_errno']	15	15	pcap_next_packet	call site	/src/libpcap/sf-pcap.c:652
15	15	2 : View List ['__errno_location', 'pcap_fmt_errmsg_for_errno']	15	15	pcap_next_packet	call site	/src/libpcap/sf-pcap.c:704
15	15	2 : View List ['__errno_location', 'pcap_fmt_errmsg_for_errno']	15	15	pcap_ng_check_header	call site	/src/libpcap/sf-pcapng.c:822

Runtime coverage analysis

Covered functions

259

Functions that are reachable but not covered

80

Reachable functions

309

Percentage of reachable functions covered

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
build/../testprogs/fuzz/fuzz_both.c	2
savefile.c	10
fmtutils.c	2
bpf_filter.c	2
extract.h	2
missing/strlcpy.c	1
pcap.c	9
gencode.c	155
build/scanner.c	24
build/grammar.c	2
scanner.l	1
nametoaddr.c	13
build/grammar.y	4
optimize.c	47

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
pcap_open_live	/src/libpcap/pcap.c	5	['char *', 'int ', 'int ', 'int ', 'char *']	7	0	193	29	12	125	0	680	599
pcap_ng_check_header	/src/libpcap/sf-pcapng.c	5	['char *', 'struct._IO_FILE *', 'int ', 'char *', 'int *']	3	0	678	72	23	39	0	250	215
netfilter_create	/src/libpcap/pcap-netfilter-linux.c	3	['char *', 'char *', 'int *']	3	0	123	20	8	58	0	249	134
pcap_lookupdev	/src/libpcap/pcap.c	1	['char *']	8	0	77	14	6	28	0	145	117
usb_create	/src/libpcap/pcap-usb-linux.c	3	['char *', 'char *', 'int *']	4	0	119	18	8	55	0	212	81
pcap_check_header	/src/libpcap/sf-pcap.c	5	['char *', 'struct._IO_FILE *', 'int ', 'char *', 'int *']	3	0	649	77	25	29	0	192	49
pcap_dump_open_append	/src/libpcap/sf-pcap.c	2	['struct.pcap.40 *', 'char *']	3	0	432	60	20	17	0	63	38

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

Functions statically reachable by fuzzers

511/600

Cyclomatic complexity statically reachable by fuzzers

3349 / 3652

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 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
pcap_open_offline_with_tstamp_precision	32	16	50.0%	['fuzz_pcap', 'fuzz_both']
yy_get_next_buffer	90	19	21.11%	['fuzz_filter', 'fuzz_both']
gen_atmmulti_abbrev	60	26	43.33%	['fuzz_filter', 'fuzz_both']

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/libpcap/build/grammar.y	['fuzz_filter', 'fuzz_both']	['fuzz_both']
/src/libpcap/pcap-netfilter-linux.c	[]	[]
/src/libpcap/sf-pcapng.c	[]	[]
/src/libpcap/bpf_filter.c	['fuzz_pcap', 'fuzz_both']	['fuzz_both']
/src/libpcap/missing/strlcpy.c	['fuzz_pcap', 'fuzz_filter', 'fuzz_both']	['fuzz_both']
/src/libpcap/pcap-util.c	[]	[]
/src/libpcap/savefile.c	['fuzz_pcap', 'fuzz_both']	['fuzz_pcap', 'fuzz_both']
/src/libpcap/scanner.l	['fuzz_filter', 'fuzz_both']	['fuzz_both']
/src/libpcap/fmtutils.c	['fuzz_pcap', 'fuzz_filter', 'fuzz_both']	[]
/src/libpcap/extract.h	['fuzz_pcap', 'fuzz_filter', 'fuzz_both']	['fuzz_pcap', 'fuzz_both']
/src/libpcap/optimize.c	['fuzz_filter', 'fuzz_both']	['fuzz_both']
/src/libpcap/build/../testprogs/fuzz/fuzz_filter.c	['fuzz_filter']	[]
/src/libpcap/build/../testprogs/fuzz/fuzz_pcap.c	['fuzz_pcap']	[]
/src/libpcap/pcap-linux.c	[]	[]
/src/libpcap/fad-getad.c	[]	[]
/src/libpcap/build/scanner.c	['fuzz_filter', 'fuzz_both']	['fuzz_both']
/src/libpcap/sf-pcap.c	[]	[]
/src/libpcap/gencode.c	['fuzz_filter', 'fuzz_both']	['fuzz_both']
/src/libpcap/nametoaddr.c	['fuzz_filter', 'fuzz_both']	['fuzz_both']
/src/libpcap/pcap-common.c	[]	[]
/src/libpcap/build/../testprogs/fuzz/fuzz_both.c	['fuzz_both']	[]
/src/libpcap/pcap.c	['fuzz_pcap', 'fuzz_filter', 'fuzz_both']	['fuzz_pcap', 'fuzz_both']
/src/libpcap/pcap-usb-linux-common.c	[]	[]
/src/libpcap/build/grammar.c	['fuzz_filter', 'fuzz_both']	['fuzz_both']
/src/libpcap/pcap-usb-linux.c	[]	[]

Directories in report

Directory
/src/libpcap/build/
/src/libpcap/build/../testprogs/fuzz/
/src/libpcap/missing/
/src/libpcap/

This section shows a chosen list of functions / methods calls and their relative coverage information. By static analysis of the target project code, all of these function call and their caller information, including the source file or class and line number that initiate the call are captured. The caller source code file or class and the line number are shown in column 2 while column 1 is the function name of that selected functions or methods call. Each occurrent of the target function call will occuply a separate row. Column 3 of each row indicate if the target function calls is statically unreachable.Column 4 lists all fuzzers (or no fuzzers at all) that have covered that particular system call in dynamic fuzzing. Those functions with low to no reachability and dynamic hit count indicate missed fuzzing logic to fuzz and track for possible code injection sinks.

Function in each files in report

Target sink	Callsite location	Reached by fuzzer