High level conclusions

Fuzzers reach 9.574% of cyclomatic complexity.

Fuzzers reach 3.962% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

321 / 8100

Cyclomatic complexity statically reachable by fuzzers

2691 / 28106

Runtime code coverage of functions

266 / 8100

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	38	13.9%
gold	[1:9]	0	0.0%
yellow	[10:29]	8	2.94%
greenyellow	[30:49]	2	0.73%
lawngreen	50+	224	82.3%
All colors	272	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	263	LLVMFuzzerTestOneInput	call site: 00263	p11_debug_message
4	66	p11_attr_copy	call site: 00066	p11_attr_copy
3	57	attrs_build	call site: 00057	p11_attrs_free
3	163	p11_kit_uri_format	call site: 00163	p11_buffer_init_full
2	3	p11_kit_uri_new	call site: 00003	vfprintf
2	54	p11_attrs_count	call site: 00054	p11_attrs_free
2	168	buffer_realloc	call site: 00168	p11_debug_precond
1	11	maybe_expand_array	call site: 00011	p11_array_free
1	30	p11_attrs_free	call site: 00030	p11_attr_clear
1	85	parse_class_attribute	call site: 00085	p11_attrs_build
1	158	p11_array_insert	call site: 00158	p11_debug_precond
1	177	p11_buffer_append	call site: 00177	p11_debug_precond

Runtime coverage analysis

Covered functions

68

Functions that are reachable but not covered

20

Reachable functions

88

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/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	6
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	88	18.5%
gold	[1:9]	3	0.63%
yellow	[10:29]	9	1.89%
greenyellow	[30:49]	3	0.63%
lawngreen	50+	372	78.3%
All colors	475	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	109	p11_asn1_cache_take	call site: 00109	p11_dict_set
6	30	p11_dict_set	call site: 00030	p11_dict_free
4	96	p11_attr_copy	call site: 00096	p11_attr_copy
4	126	sink_object	call site: 00126	p11_message
4	310	p11_constant_reverse	call site: 00310	p11_dict_set
3	19	p11_asn1_defs_load	call site: 00019	p11_dict_free
3	134	p11_message	call site: 00134	p11_message
3	434	certificate_to_attributes	call site: 00434	public_key_to_attributes
3	445	p11_persist_read	call site: 00445	p11_lexer_done
2	7	p11_asn1_defs_load	call site: 00007	p11_hash_murmur3
2	55	p11_array_push	call site: 00055	p11_debug_precond
2	70	p11_asn1_create	call site: 00070	p11_debug_precond

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	783	68.3%
gold	[1:9]	139	12.1%
yellow	[10:29]	20	1.74%
greenyellow	[30:49]	4	0.34%
lawngreen	50+	199	17.3%
All colors	1145	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	219	p11_rpc_buffer_get_uint64	call site: 00219	rpc_C_GetMechanismList
103	871	rpc_C_EncryptMessageBegin	call site: 00871	rpc_C_MessageDecryptInit
80	591	rpc_C_DigestInit	call site: 00591	rpc_C_SignInit
54	709	rpc_C_VerifyRecoverInit	call site: 00709	rpc_C_GenerateKey
50	813	rpc_C_SeedRandom	call site: 00813	rpc_C_MessageEncryptInit
31	982	rpc_C_MessageVerifyInit	call site: 00982	rpc_C_VerifyMessage
30	139	rpc_C_Initialize	call site: 00139	rpc_C_GetInfo
26	524	rpc_C_EncryptInit	call site: 00524	rpc_C_Encrypt
26	558	rpc_C_DecryptInit	call site: 00558	rpc_C_Decrypt
24	414	rpc_C_CreateObject	call site: 00414	rpc_C_CopyObject
22	679	rpc_C_VerifyInit	call site: 00679	rpc_C_Verify
17	176	p11_rpc_buffer_add_uint64	call site: 00176	rpc_C_GetSlotList

Runtime coverage analysis

Covered functions

137

Functions that are reachable but not covered

141

Reachable functions

227

Percentage of reachable functions covered

37.89%

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	32
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	454	0	3425	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	245	44	13	78	0	361	89

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

Functions statically reachable by fuzzers

505 / 8100

Cyclomatic complexity statically reachable by fuzzers

4100 / 28106

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', 'attrs_build', 'p11_kit_uri_format', 'p11_kit_uri_new', 'p11_attrs_count', 'buffer_realloc', 'maybe_expand_array', 'p11_attrs_free', 'parse_class_attribute']

./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_message', 'certificate_to_attributes', 'p11_persist_read']

./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_EncryptMessageBegin', 'rpc_C_DigestInit', 'rpc_C_VerifyRecoverInit', 'rpc_C_SeedRandom', 'rpc_C_MessageVerifyInit', 'rpc_C_Initialize', 'rpc_C_EncryptInit', 'rpc_C_DecryptInit', 'rpc_C_CreateObject']

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

Directories in report

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