High level conclusions

Fuzzers reach 9.611% of cyclomatic complexity.

Fuzzers reach 3.974% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

322 / 8101

Cyclomatic complexity statically reachable by fuzzers

2704 / 28132

Runtime code coverage of functions

254 / 8101

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

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	15.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	1	1.92%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	43	82.6%
All colors	52	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
2	2	p11_lexer_init	call site: 00002	vfprintf
2	26	p11_message	call site: 00026	p11_message
1	17	p11_lexer_msg	call site: 00017	p11_message
1	19	p11_message	call site: 00019	fprintf
1	24	p11_debug_message	call site: 00024	fprintf
1	47	p11_lexer_next	call site: 00047	p11_debug_precond

Runtime coverage analysis

Covered functions

12

Functions that are reachable but not covered

13

Reachable functions

24

Percentage of reachable functions covered

45.83%

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/conf_fuzzer.c	1
common/lexer.c	5
common/debug.c	2
common/compat.c	2
common/message.c	2

Fuzzer: uri_fuzzer

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	54	18.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	6	2.09%
greenyellow	[30:49]	2	0.69%
lawngreen	50+	225	78.3%
All colors	287	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	278	LLVMFuzzerTestOneInput	call site: 00278	p11_debug_message
4	67	p11_attr_copy	call site: 00067	p11_attr_copy
4	255	p11_kit_uri_format	call site: 00255	p11_buffer_uninit
3	58	attrs_build	call site: 00058	p11_attrs_free
3	165	p11_kit_uri_format	call site: 00165	p11_buffer_init_full
3	199	p11_kit_uri_format	call site: 00199	p11_buffer_uninit
2	3	p11_kit_uri_new	call site: 00003	vfprintf
2	55	p11_attrs_count	call site: 00055	p11_attrs_free
2	159	p11_array_insert	call site: 00159	p11_debug_precond
2	170	buffer_realloc	call site: 00170	p11_debug_precond
2	207	format_raw_string	call site: 00207	p11_buffer_uninit
2	214	format_ulong	call site: 00214	p11_buffer_uninit

Runtime coverage analysis

Covered functions

68

Functions that are reachable but not covered

21

Reachable functions

89

Percentage of reachable functions covered

76.4%

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/uri_fuzzer.c	1
p11-kit/uri.c	39
common/debug.c	2
common/array.c	5
common/compat.c	3
common/attrs.c	11
common/url.c	2
common/buffer.c	7
p11-kit/util.c	1

Fuzzer: persist_fuzzer

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	130	25.6%
gold	[1:9]	4	0.78%
yellow	[10:29]	4	0.78%
greenyellow	[30:49]	2	0.39%
lawngreen	50+	367	72.3%
All colors	507	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
13	117	p11_asn1_cache_take	call site: 00117	p11_dict_set
6	30	p11_dict_set	call site: 00030	p11_dict_free
4	101	p11_attr_copy	call site: 00101	p11_attr_copy
4	134	sink_object	call site: 00134	p11_message
4	150	sink_object	call site: 00150	p11_attrs_free
4	339	p11_constant_reverse	call site: 00339	p11_dict_set
3	19	p11_asn1_defs_load	call site: 00019	p11_dict_free
3	47	p11_attrs_free	call site: 00047	p11_dict_free
3	51	p11_parser_new	call site: 00051	p11_dict_free
3	59	p11_array_push	call site: 00059	p11_array_free
3	112	p11_attrs_find_valid	call site: 00112	p11_attrs_free
3	142	p11_message	call site: 00142	p11_message

Runtime coverage analysis

Covered functions

106

Functions that are reachable but not covered

34

Reachable functions

122

Percentage of reachable functions covered

72.13%

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/persist_fuzzer.c	1
trust/parser.c	17
common/asn1.c	12
common/dict.c	14
common/hash.c	1
common/debug.c	2
common/array.c	5
common/attrs.c	16
common/compat.c	4
common/message.c	2
common/pem.c	4
common/base64.c	1
common/oid.c	1
common/persist.c	16
common/constants.c	5
common/lexer.c	5
common/url.c	1
common/path.c	1

Fuzzer: rpc_fuzzer

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	824	72.0%
gold	[1:9]	110	9.62%
yellow	[10:29]	16	1.39%
greenyellow	[30:49]	25	2.18%
lawngreen	50+	168	14.6%
All colors	1143	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
170	218	p11_rpc_buffer_get_uint64	call site: 00218	rpc_C_GetMechanismList
161	810	rpc_C_SeedRandom	call site: 00810	rpc_C_MessageEncryptInit
84	676	rpc_C_VerifyInit	call site: 00676	rpc_C_GenerateKey
80	588	rpc_C_DigestInit	call site: 00588	rpc_C_SignInit
46	979	rpc_C_MessageVerifyInit	call site: 00979	rpc_C_VerifyMessage
29	139	rpc_C_Initialize	call site: 00139	rpc_C_GetInfo
29	518	proto_read_mechanism	call site: 00518	rpc_C_Encrypt
26	555	rpc_C_DecryptInit	call site: 00555	rpc_C_Decrypt
24	413	rpc_C_CreateObject	call site: 00413	rpc_C_CopyObject
19	454	proto_read_attribute_buffer_array	call site: 00454	call_ready
19	489	rpc_C_FindObjectsInit	call site: 00489	rpc_C_EncryptInit
17	175	p11_rpc_buffer_add_uint64	call site: 00175	rpc_C_GetSlotList

Runtime coverage analysis

Covered functions

125

Functions that are reachable but not covered

146

Reachable functions

228

Percentage of reachable functions covered

35.96%

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/rpc_fuzzer.c	1
common/mock.c	4
common/library.c	5
common/debug.c	4
common/compat.c	1
common/buffer.c	7
p11-kit/virtual.c	1
p11-kit/rpc-server.c	110
common/message.c	3
p11-kit/rpc-message.c	33
common/dict.c	9
common/attrs.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
p11_kit_remote_serve_tokens	/src/p11-kit/p11-kit/rpc-server.c	5	['N/A', 'size_t', 'N/A', 'int', 'int']	14	0	546	110	36	455	0	3431	1130
log_C_GetAttributeValue	/src/p11-kit/p11-kit/log.c	5	['N/A', 'size_t', 'size_t', 'N/A', 'size_t']	7	0	94	9	3	42	0	329	264
parse_openssl_trusted_certificate	/src/p11-kit/trust/parser.c	3	['N/A', 'N/A', 'size_t']	9	0	263	44	14	78	0	366	94

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

Functions statically reachable by fuzzers

506 / 8101

Cyclomatic complexity statically reachable by fuzzers

4118 / 28132

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/conf_fuzzer.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=['p11_lexer_init', 'p11_message', 'p11_lexer_msg', 'p11_debug_message', 'p11_lexer_next']

./fuzz/uri_fuzzer.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=['LLVMFuzzerTestOneInput', 'p11_attr_copy', 'p11_kit_uri_format', 'attrs_build', 'p11_kit_uri_new', 'p11_attrs_count', 'p11_array_insert', 'buffer_realloc']

./fuzz/persist_fuzzer.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=['p11_asn1_cache_take', 'p11_dict_set', 'p11_attr_copy', 'sink_object', 'p11_constant_reverse', 'p11_asn1_defs_load', 'p11_attrs_free', 'p11_parser_new', 'p11_array_push']

./fuzz/rpc_fuzzer.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=['p11_rpc_buffer_get_uint64', 'rpc_C_SeedRandom', 'rpc_C_VerifyInit', 'rpc_C_DigestInit', 'rpc_C_MessageVerifyInit', 'rpc_C_Initialize', 'proto_read_mechanism', 'rpc_C_DecryptInit', 'rpc_C_CreateObject', 'proto_read_attribute_buffer_array']

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
parse_environ_flags	38	12	31.57%	['rpc_fuzzer']
mechanism_has_no_parameters	131	5	3.816%	['rpc_fuzzer']
p11_rpc_server_handle	139	44	31.65%	['rpc_fuzzer']
proto_read_attribute_buffer_array	44	24	54.54%	['rpc_fuzzer']

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/p11-kit/common/url.c	['uri_fuzzer', 'persist_fuzzer']	['uri_fuzzer', 'persist_fuzzer']
/src/p11-kit/./p11-kit/virtual-stack-generated.h	[]	[]
/src/p11-kit/common/attrs.c	['uri_fuzzer', 'persist_fuzzer', 'rpc_fuzzer']	['uri_fuzzer', 'persist_fuzzer', 'rpc_fuzzer']
/src/p11-kit/trust/parser.c	['persist_fuzzer']	['persist_fuzzer']
/src/p11-kit/common/lexer.c	['conf_fuzzer', 'persist_fuzzer']	['conf_fuzzer', 'persist_fuzzer']
/src/p11-kit/common/message.c	['conf_fuzzer', 'persist_fuzzer', 'rpc_fuzzer']	['conf_fuzzer', 'persist_fuzzer', 'rpc_fuzzer']
/src/p11-kit/p11-kit/log.c	[]	[]
/src/p11-kit/common/hash.c	['persist_fuzzer']	['persist_fuzzer']
/src/p11-kit/common/array.c	['uri_fuzzer', 'persist_fuzzer']	['uri_fuzzer', 'persist_fuzzer']
/src/p11-kit/p11-kit/rpc-transport.c	[]	[]
/src/p11-kit/p11-kit/modules.c	[]	[]
/src/p11-kit/common/persist.c	['persist_fuzzer']	['persist_fuzzer']
/src/p11-kit/p11-kit/virtual.c	['rpc_fuzzer']	['rpc_fuzzer']
/src/p11-kit/p11-kit/rpc-server.c	['rpc_fuzzer']	['rpc_fuzzer']
/src/p11-kit/common/mock.c	['rpc_fuzzer']	['rpc_fuzzer']
/src/p11-kit/common/path.c	['persist_fuzzer']	['persist_fuzzer']
/src/p11-kit/common/debug.c	['conf_fuzzer', 'uri_fuzzer', 'persist_fuzzer', 'rpc_fuzzer']	['conf_fuzzer', 'persist_fuzzer', 'rpc_fuzzer']
/src/p11-kit/./p11-kit/virtual-fixed-closures.h	[]	[]
/src/p11-kit/./p11-kit/virtual-base-generated.h	[]	[]
/src/p11-kit/./p11-kit/proxy-generated.h	[]	[]
/src/p11-kit/common/vsock.c	[]	[]
/src/p11-kit/common/base64.c	['persist_fuzzer']	['persist_fuzzer']
/src/p11-kit/common/asn1.c	['persist_fuzzer']	['persist_fuzzer']
/src/p11-kit/common/oid.c	['persist_fuzzer']	['persist_fuzzer']
/src/p11-kit/common/constants.c	['persist_fuzzer']	['persist_fuzzer']
/src/p11-kit/common/dict.c	['persist_fuzzer', 'rpc_fuzzer']	['persist_fuzzer', 'rpc_fuzzer']
/src/p11-kit/p11-kit/rpc-message.c	['rpc_fuzzer']	['rpc_fuzzer']
/src/p11-kit/p11-kit/proxy.c	[]	[]
/src/p11-kit/p11-kit/pin.c	[]	[]
/src/p11-kit/p11-kit/messages.c	[]	[]
/src/p11-kit/./fuzz/persist_fuzzer.c	['persist_fuzzer']	[]
/src/p11-kit/./p11-kit/virtual-ffi-generated.h	[]	[]
/src/p11-kit/p11-kit/rpc-client.c	[]	[]
/src/p11-kit/common/argv.c	[]	[]
/src/p11-kit/./fuzz/uri_fuzzer.c	['uri_fuzzer']	[]
/src/p11-kit/p11-kit/util.c	['uri_fuzzer']	['uri_fuzzer']
/src/p11-kit/p11-kit/filter.c	[]	[]
/src/p11-kit/p11-kit/conf.c	[]	[]
/src/p11-kit/./fuzz/conf_fuzzer.c	['conf_fuzzer']	[]
/src/p11-kit/common/library.c	['rpc_fuzzer']	['rpc_fuzzer']
/src/p11-kit/common/buffer.c	['uri_fuzzer', 'rpc_fuzzer']	['uri_fuzzer', 'rpc_fuzzer']
/src/p11-kit/./fuzz/rpc_fuzzer.c	['rpc_fuzzer']	[]
/src/p11-kit/p11-kit/uri.c	['uri_fuzzer']	['uri_fuzzer']
/src/p11-kit/common/compat.c	['conf_fuzzer', 'uri_fuzzer', 'persist_fuzzer', 'rpc_fuzzer']	['conf_fuzzer', 'uri_fuzzer', 'persist_fuzzer', 'rpc_fuzzer']
/src/p11-kit/p11-kit/iter.c	[]	[]
/src/p11-kit/common/pem.c	['persist_fuzzer']	['persist_fuzzer']

Directories in report

Directory
/src/p11-kit/./fuzz/
/src/p11-kit/common/
/src/p11-kit/p11-kit/
/src/p11-kit/trust/
/src/p11-kit/./p11-kit/