High level conclusions

Fuzzer FuzzExtens is blocked:

The runtime code coverage of FuzzExtens covers 9.259% 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 23.95% of cyclomatic complexity.

Fuzzers reach 16.96% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

28 / 165

Cyclomatic complexity statically reachable by fuzzers

184 / 768

Runtime code coverage of functions

14 / 165

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

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	71	91.0%
gold	[1:9]	1	1.28%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	7.69%
All colors	78	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
209	209	4 : View List ['AES_SIV_Decrypt', 'nts_unlock_cookielock', 'memcmp', 'nts_lock_cookielock']	209	209	nts_unpack_cookie	call site: 00006	/src/ntpsec/build/main/../../ntpd/nts_cookie.c:383
0	0	None	91	259	extens_server_recv	call site: 00006	/src/ntpsec/build/main/../../ntpd/nts_extens.c:184
0	0	None	91	259	extens_server_recv	call site: 00006	/src/ntpsec/build/main/../../ntpd/nts_extens.c:205
0	0	None	0	0	extens_server_recv	call site: 00005	/src/ntpsec/build/main/../../ntpd/nts_extens.c:173
0	0	None	0	0	extens_server_recv	call site: 00077	/src/ntpsec/build/main/../../ntpd/nts_extens.c:259

Runtime coverage analysis

Covered functions

5

Functions that are reachable but not covered

49

Reachable functions

54

Percentage of reachable functions covered

9.26%

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/FuzzExtens.c	1
build/main/../../ntpd/nts_extens.c	1
build/main/../../ntpd/nts.c	3
build/main/../../ntpd/nts_cookie.c	3
build/main/../../libntp/msyslog.c	3
build/main/../../libntp/strl_obsd.c	1
build/main/../../libaes_siv/aes_siv.c	11

Fuzzer: FuzzServer

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	11.7%
gold	[1:9]	2	5.88%
yellow	[10:29]	4	11.7%
greenyellow	[30:49]	1	2.94%
lawngreen	50+	23	67.6%
All colors	34	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	18	34	addto_syslog	call site: 00010	/src/ntpsec/build/main/../../libntp/msyslog.c:105
0	0	None	16	32	addto_syslog	call site: 00010	/src/ntpsec/build/main/../../libntp/msyslog.c:114
0	0	None	16	32	addto_syslog	call site: 00011	/src/ntpsec/build/main/../../libntp/msyslog.c:120
0	0	None	16	16	addto_syslog	call site: 00011	/src/ntpsec/build/main/../../libntp/msyslog.c:127
0	0	None	14	14	addto_syslog	call site: 00012	/src/ntpsec/build/main/../../libntp/msyslog.c:132
0	0	None	12	12	addto_syslog	call site: 00018	/src/ntpsec/build/main/../../libntp/msyslog.c:138
0	0	None	0	0	humanlogtime	call site: 00014	/src/ntpsec/build/main/../../libntp/msyslog.c:55

Runtime coverage analysis

Covered functions

8

Functions that are reachable but not covered

14

Reachable functions

22

Percentage of reachable functions covered

36.36%

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/FuzzServer.c	1
build/main/../../ntpd/nts_server.c	1
build/main/../../ntpd/nts.c	3
build/main/../../libntp/msyslog.c	3
build/main/../../libntp/strl_obsd.c	1

Fuzzer: FuzzClient

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	13.4%
gold	[1:9]	3	4.47%
yellow	[10:29]	13	19.4%
greenyellow	[30:49]	1	1.49%
lawngreen	50+	41	61.1%
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
0	0	None	18	34	addto_syslog	call site: 00012	/src/ntpsec/build/main/../../libntp/msyslog.c:105
0	0	None	16	32	addto_syslog	call site: 00012	/src/ntpsec/build/main/../../libntp/msyslog.c:114
0	0	None	16	32	addto_syslog	call site: 00013	/src/ntpsec/build/main/../../libntp/msyslog.c:120
0	0	None	16	16	addto_syslog	call site: 00013	/src/ntpsec/build/main/../../libntp/msyslog.c:127
0	0	None	14	14	addto_syslog	call site: 00014	/src/ntpsec/build/main/../../libntp/msyslog.c:132
0	0	None	12	12	addto_syslog	call site: 00020	/src/ntpsec/build/main/../../libntp/msyslog.c:138
0	0	None	9	9	socktoa_r	call site: 00049	/src/ntpsec/build/main/../../libntp/socktoa.c:43
0	0	None	0	0	humanlogtime	call site: 00016	/src/ntpsec/build/main/../../libntp/msyslog.c:55
0	0	None	0	0	nts_server_lookup	call site: 00045	/src/ntpsec/build/main/../../ntpd/nts_client.c:810

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

22

Reachable functions

33

Percentage of reachable functions covered

33.33%

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/FuzzClient.c	1
build/main/../../ntpd/nts_client.c	2
build/main/../../ntpd/nts.c	4
build/main/../../libntp/msyslog.c	3
build/main/../../libntp/strl_obsd.c	1
build/main/../../libntp/socktoa.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
nts_probe	/src/ntpsec/build/main/../../ntpd/nts_client.c	1	['struct.peer *']	3	0	375	42	16	120	0	385	266
nts_ke_listener	/src/ntpsec/build/main/../../ntpd/nts_server.c	1	['char *']	4	0	370	15	7	108	2	338	84
setup_logfile	/src/ntpsec/build/main/../../libntp/msyslog.c	1	['char *']	3	0	72	16	7	28	0	117	55

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

Functions statically reachable by fuzzers

80 / 165

Cyclomatic complexity statically reachable by fuzzers

453 / 768

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
nts_unpack_cookie	64	12	18.75%	['FuzzExtens']
socktoa_r	32	16	50.0%	['FuzzClient']

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/ntpsec/build/main/../../ntpd/nts.c	['FuzzExtens', 'FuzzServer', 'FuzzClient']	[]
/src/ntpsec/build/main/../../ntpd/nts_client.c	['FuzzClient']	[]
/src/ntpsec/build/main/../../include/ntp_fp.h	[]	[]
/src/ntpsec/fuzz/setup.c	[]	[]
/src/ntpsec/build/main/../../libntp/msyslog.c	['FuzzExtens', 'FuzzServer', 'FuzzClient']	[]
/src/ntpsec/build/main/../../libntp/assert.c	[]	[]
/src/ntpsec/build/main/../../libntp/lib_strbuf.c	[]	[]
/usr/include/openssl/x509v3.h	[]	[]
/src/ntpsec/fuzz/FuzzExtens.c	['FuzzExtens']	['FuzzExtens']
/src/ntpsec/build/main/../../libntp/ntp_calendar.c	[]	[]
/src/ntpsec/fuzz/FuzzServer.c	['FuzzServer']	['FuzzServer']
/src/ntpsec/build/main/../../libntp/emalloc.c	[]	[]
/src/ntpsec/build/main/../../libntp/ntp_random.c	[]	[]
/src/ntpsec/build/main/../../libntp/socktoa.c	['FuzzClient']	[]
/src/ntpsec/build/main/../../libntp/strl_obsd.c	['FuzzExtens', 'FuzzServer', 'FuzzClient']	[]
/src/ntpsec/build/main/../../libntp/timespecops.c	[]	[]
/src/ntpsec/fuzz/FuzzClient.c	['FuzzClient']	['FuzzClient']
/src/ntpsec/build/main/../../libaes_siv/aes_siv.c	['FuzzExtens']	[]
/src/ntpsec/build/main/../../ntpd/nts_server.c	['FuzzServer']	[]
/src/ntpsec/build/main/../../ntpd/nts_extens.c	['FuzzExtens']	[]
/src/ntpsec/build/main/../../ntpd/nts_cookie.c	['FuzzExtens']	[]

Directories in report

Directory
/src/ntpsec/build/main/../../include/
/src/ntpsec/fuzz/
/src/ntpsec/build/main/../../ntpd/
/src/ntpsec/build/main/../../libaes_siv/
/src/ntpsec/build/main/../../libntp/
/usr/include/openssl/