High level conclusions

Fuzzers reach 43.84% of cyclomatic complexity.

Fuzzers reach 28.37% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

122 / 430

Cyclomatic complexity statically reachable by fuzzers

1467 / 3346

Runtime code coverage of functions

188 / 430

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

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	11	14.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	1	1.31%
greenyellow	[30:49]	9	11.8%
lawngreen	50+	55	72.3%
All colors	76	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
7	45	regex_match	call site: 00045	fprintf
2	38	regex_match	call site: 00038	pcre2_get_error_message_8
1	33	sentrypeer_config_new	call site: 00033	sentrypeer_config_destroy
1	58	regex_match	call site: 00058	fprintf

Runtime coverage analysis

Covered functions

10

Functions that are reachable but not covered

18

Reachable functions

28

Percentage of reachable functions covered

35.71%

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
sentrypeer/tests/fuzz/fuzz_http_input.c	1
sentrypeerconf.c	2
sentrypeerutils.c	6
sentrypeerregex_match.c	1

Fuzzer: fuzz_json_bad_actor

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	8	7.27%
gold	[1:9]	2	1.81%
yellow	[10:29]	56	50.9%
greenyellow	[30:49]	31	28.1%
lawngreen	50+	13	11.8%
All colors	110	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
1	33	sentrypeer_config_new	call site: 00033	sentrypeer_config_destroy
1	36	LLVMFuzzerTestOneInput	call site: 00036	fprintf
1	42	json_to_bad_actor	call site: 00042	json_delete
1	51	event_timestamp	call site: 00051	perror
1	56	event_timestamp	call site: 00056	perror
1	98	json_to_bad_actor	call site: 00098	fprintf
1	102	bad_actor_to_json	call site: 00102	fprintf
1	105	bad_actor_to_json	call site: 00105	fprintf

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

21

Reachable functions

32

Percentage of reachable functions covered

34.38%

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
sentrypeer/tests/fuzz/fuzz_json_bad_actor.c	1
sentrypeerconf.c	2
sentrypeerutils.c	4
sentrypeerjson_logger.c	2
/usr/include/jansson.h	1
sentrypeerbad_actor.c	2

Fuzzer: fuzz_sip_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	42	6.28%
gold	[1:9]	7	1.04%
yellow	[10:29]	7	1.04%
greenyellow	[30:49]	7	1.04%
lawngreen	50+	605	90.5%
All colors	668	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
8	227	osip_trace	call site: 00227	syslog
5	221	osip_trace	call site: 00221	snprintf
2	73	osip_message_init	call site: 00073	osip_message_free
2	217	osip_trace	call site: 00217	strrchr
2	237	osip_trace	call site: 00237	osip_message_free
2	338	__osip_message_startline_parsereq	call site: 00338	osip_uri_free
2	588	_osip_message_to_str	call site: 00588	osip_strdup
1	38	event_timestamp	call site: 00038	perror
1	43	event_timestamp	call site: 00043	perror
1	211	parser_init	call site: 00211	osip_trace
1	241	osip_message_parse	call site: 00241	osip_trace
1	270	osip_uri_parse	call site: 00270	strncasecmp

Runtime coverage analysis

Covered functions

183

Functions that are reachable but not covered

33

Reachable functions

149

Percentage of reachable functions covered

77.85%

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
sentrypeer/tests/fuzz/fuzz_sip_parser.c	1
sentrypeerconf.c	2
sentrypeerutils.c	4
sentrypeerbad_actor.c	2
sentrypeersip_parser.c	1
osiposipparser2/osip_message.c	2
osiposipparser2/osip_list.c	9
osiposipparser2/osip_uri.c	19
osiposipparser2/osip_content_type.c	4
osiposipparser2/osip_authorization.c	1
osiposipparser2/osip_call_id.c	1
osiposipparser2/osip_accept_encoding.c	1
osiposipparser2/osip_call_info.c	1
osiposipparser2/osip_content_length.c	4
osiposipparser2/osip_authentication_info.c	1
osiposipparser2/osip_contact.c	1
osiposipparser2/osip_from.c	2
osiposipparser2/osip_cseq.c	1
osiposipparser2/osip_www_authenticate.c	1
osiposipparser2/osip_record_route.c	1
osiposipparser2/osip_route.c	1
osiposipparser2/osip_to.c	1
osiposipparser2/osip_via.c	1
osiposipparser2/osip_header.c	5
osiposipparser2/osip_body.c	10
osiposipparser2/osip_parser_cfg.c	4
osiposipparser2/osip_port.c	14
osiposipparser2/osip_message_parse.c	12
osiposipparser2/osip_message_to_str.c	9

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
osip_message_clone	/src/osip/src/osipparser2/osip_message.c	2	['N/A', 'N/A']	4	0	814	108	48	67	0	623	289
bad_actor_log	/src/sentrypeer/src/bad_actor.c	2	['N/A', 'N/A']	5	0	113	19	8	46	0	187	136
osip_message_set_authorization	/src/osip/src/osipparser2/osip_authorization.c	2	['N/A', 'N/A']	4	0	87	15	7	16	0	210	112
process_cli	/src/sentrypeer/src/conf.c	3	['N/A', 'int', 'N/A']	3	0	221	35	36	18	0	116	88
osip_message_set_contact	/src/osip/src/osipparser2/osip_contact.c	2	['N/A', 'N/A']	8	0	79	13	6	37	0	415	70
osip_message_set_via	/src/osip/src/osipparser2/osip_via.c	2	['N/A', 'N/A']	6	0	79	13	6	26	0	246	55
osip_authorization_to_str	/src/osip/src/osipparser2/osip_authorization.c	2	['N/A', 'N/A']	1	0	985	158	54	3	0	60	54
osip_message_set_authentication_info	/src/osip/src/osipparser2/osip_authentication_info.c	2	['N/A', 'N/A']	4	0	87	15	7	16	0	181	52
osip_message_set_www_authenticate	/src/osip/src/osipparser2/osip_www_authenticate.c	2	['N/A', 'N/A']	4	0	87	15	7	16	0	180	51
osip_authentication_info_to_str	/src/osip/src/osipparser2/osip_authentication_info.c	2	['N/A', 'N/A']	1	0	673	109	38	3	0	44	38

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

Functions statically reachable by fuzzers

182 / 430

Cyclomatic complexity statically reachable by fuzzers

2364 / 3346

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.

sentrypeer/tests/fuzz/fuzz_http_input.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=['regex_match', 'sentrypeer_config_new']

sentrypeer/tests/fuzz/fuzz_json_bad_actor.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=['sentrypeer_config_new', 'LLVMFuzzerTestOneInput', 'json_to_bad_actor', 'event_timestamp', 'bad_actor_to_json']

sentrypeer/tests/fuzz/fuzz_sip_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=['osip_trace', 'osip_message_init', '__osip_message_startline_parsereq', '_osip_message_to_str', 'event_timestamp', 'parser_init']

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
osip_list_add	57	30	52.63%	['fuzz_sip_parser']

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/sentrypeer/src/utils.c	['fuzz_http_input', 'fuzz_json_bad_actor', 'fuzz_sip_parser']	['fuzz_http_input', 'fuzz_json_bad_actor', 'fuzz_sip_parser']
/src/osip/src/osipparser2/osip_route.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/osip/src/osipparser2/osip_via.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/osip/src/osipparser2/osip_content_type.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/osip/src/osipparser2/osip_mime_version.c	[]	[]
/src/osip/src/osipparser2/osip_to.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/osip/src/osipparser2/osip_body.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/usr/include/jansson.h	['fuzz_json_bad_actor']	[]
/src/osip/src/osipparser2/osip_proxy_authenticate.c	[]	[]
/src/osip/src/osipparser2/osip_uri.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/osip/src/osipparser2/osip_list.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/osip/src/osipparser2/osip_authentication_info.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/sentrypeer/tests/fuzz/fuzz_http_input.c	['fuzz_http_input']	['fuzz_http_input']
/src/osip/src/osipparser2/osip_call_info.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/osip/src/osipparser2/osip_message_parse.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/osip/src/osipparser2/osip_alert_info.c	[]	[]
/src/osip/src/osipparser2/osip_contact.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/osip/src/osipparser2/osip_header.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/osip/src/osipparser2/osip_message.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/osip/src/osipparser2/osip_parser_cfg.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/osip/src/osipparser2/osip_accept_language.c	[]	[]
/src/osip/src/osipparser2/osip_from.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/sentrypeer/src/bad_actor.c	['fuzz_json_bad_actor', 'fuzz_sip_parser']	['fuzz_json_bad_actor', 'fuzz_sip_parser']
/src/sentrypeer/src/conf.c	['fuzz_http_input', 'fuzz_json_bad_actor', 'fuzz_sip_parser']	['fuzz_http_input', 'fuzz_json_bad_actor', 'fuzz_sip_parser']
/src/sentrypeer/src/json_logger.c	['fuzz_json_bad_actor']	['fuzz_json_bad_actor']
/src/sentrypeer/src/sip_parser.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/sentrypeer/src/database.c	[]	[]
/src/osip/src/osipparser2/osip_accept_encoding.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/osip/src/osipparser2/osip_www_authenticate.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/sentrypeer/src/regex_match.c	['fuzz_http_input']	['fuzz_http_input']
/src/osip/src/osipparser2/osip_message_to_str.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/osip/src/osipparser2/osip_content_length.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/osip/src/osipparser2/osip_accept.c	[]	[]
/src/sentrypeer/tests/fuzz/fuzz_sip_parser.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/osip/src/osipparser2/osip_authorization.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/sentrypeer/tests/fuzz/fuzz_json_bad_actor.c	['fuzz_json_bad_actor']	['fuzz_json_bad_actor']
/src/osip/src/osipparser2/osip_port.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/osip/src/osipparser2/osip_error_info.c	[]	[]
/src/osip/src/osipparser2/osip_record_route.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/osip/src/osipparser2/osip_call_id.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/osip/src/osipparser2/osip_proxy_authentication_info.c	[]	[]
/src/osip/src/osipparser2/osip_proxy_authorization.c	[]	[]
/src/osip/src/osipparser2/osip_allow.c	[]	[]
/src/osip/src/osipparser2/osip_cseq.c	['fuzz_sip_parser']	['fuzz_sip_parser']
/src/osip/src/osipparser2/osip_content_encoding.c	[]	[]

Directories in report

Directory
/src/sentrypeer/src/
/src/sentrypeer/tests/fuzz/
/src/osip/src/osipparser2/
/usr/include/