High level conclusions

Fuzzers reach 85.22% code coverage.

Fuzzers reach 31.21% of cyclomatic complexity.

Fuzzers reach 29.06% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

59 / 203

Cyclomatic complexity statically reachable by fuzzers

305 / 977

Runtime code coverage of functions

173 / 203

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	Fuzzers runtime hit	Func lines hit %	I Count	BB Count	Cyclomatic complexity	Functions reached	Reached by functions	Accumulated cyclomatic complexity	Undiscovered complexity

Fuzzer: fuzz_simpletlv

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	1	7.69%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	12	92.3%
All colors	13	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	4	16	simpletlv_free	call site: 00009	/work/meson/../../src/libcacard/src/simpletlv.c:268
0	0	None	0	0	lebytes2ushort	call site: 00004	/work/meson/../../src/libcacard/src/common.c:45

Runtime coverage analysis

Covered functions

6

Functions that are reachable but not covered

5

Reachable functions

11

Percentage of reachable functions covered

54.55%

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/fuzz_simpletlv.c	1
src/simpletlv.c	3
src/common.c	2

Fuzzer: fuzz_options

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	0	0.0%
gold	[1:9]	6	8.45%
yellow	[10:29]	8	11.2%
greenyellow	[30:49]	1	1.40%
lawngreen	50+	56	78.8%
All colors	71	100

Runtime coverage analysis

Covered functions

6

Functions that are reachable but not covered

10

Reachable functions

16

Percentage of reachable functions covered

37.5%

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/fuzz_options.c	1
src/vcard_emul_nss.c	4
src/vcard_emul_type.c	1

Fuzzer: fuzz_xfer

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	24	16.4%
gold	[1:9]	8	5.47%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	3	2.05%
lawngreen	50+	111	76.0%
All colors	146	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
26	152	5 : View List ['simpletlv_parse', 'g_free', 'simpletlv_free', 'cac_create_tl_file', 'cac_create_val_file']	26	274	cac_passthrough_container_process_apdu	call site: 00000	/work/meson/../../src/libcacard/src/cac.c:727
8	19	4 : View List ['acr_applet_object_encode', 'memcmp', 'g_free', 'g_malloc_n']	8	19	cac_aca_get_applet_acr_coid	call site: 00000	/work/meson/../../src/libcacard/src/cac-aca.c:827
6	12	2 : View List ['vcard_get_login_count', 'vcard_response_new_status_bytes']	8	30	vcard7816_vm_process_apdu	call site: 00096	/work/meson/../../src/libcacard/src/card_7816.c:705
4	49	4 : View List ['strcmp', 'vreader_list_get_reader', 'vreader_free', 'vreader_list_get_next']	4	53	vreader_get_reader_by_name	call site: 00000	/work/meson/../../src/libcacard/src/vreader.c:499
2	47	3 : View List ['vreader_list_get_reader', 'vreader_free', 'vreader_list_get_next']	2	51	vreader_get_reader_by_id	call site: 00027	/work/meson/../../src/libcacard/src/vreader.c:479
2	27	2 : View List ['vcard_emul_map_error', 'PORT_GetError']	6	31	vcard_emul_rsa_op	call site: 00000	/work/meson/../../src/libcacard/src/vcard_emul_nss.c:355
2	2	1 : View List ['g_malloc']	20	95	vcard_emul_rsa_op	call site: 00000	/work/meson/../../src/libcacard/src/vcard_emul_nss.c:275
2	2	1 : View List ['g_log']	6	14	get_properties	call site: 00000	/work/meson/../../src/libcacard/src/cac.c:230
2	2	1 : View List ['g_log']	2	2	LLVMFuzzerInitialize	call site: 00000	/work/meson/../../src/libcacard/fuzz/fuzz_xfer.c:127
2	2	1 : View List ['g_log']	2	2	cac_card_init	call site: 00000	/work/meson/../../src/libcacard/src/cac.c:2273
2	2	1 : View List ['g_free']	2	2	cac_create_file	call site: 00000	/work/meson/../../src/libcacard/src/cac.c:142
2	2	1 : View List ['PK11_IsLoggedIn']	2	2	vcard_emul_is_logged_in	call site: 00099	/work/meson/../../src/libcacard/src/vcard_emul_nss.c:468

Runtime coverage analysis

Covered functions

171

Functions that are reachable but not covered

23

Reachable functions

69

Percentage of reachable functions covered

66.67%

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
fuzz/fuzz_xfer.c	1
src/vreader.c	13
src/vcard.c	13
src/card_7816.c	17
src/common.c	2
src/vcard_emul_nss.c	5

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
LLVMFuzzerInitialize	/work/meson/../../src/libcacard/fuzz/fuzz_xfer.c	2	['int *', 'char ***']	6	0	50	9	3	262	0	976	763

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

Functions statically reachable by fuzzers

189 / 203

Cyclomatic complexity statically reachable by fuzzers

930 / 977

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
vcard_make_response	126	31	24.60%	['fuzz_xfer']
vcard_emul_init	133	72	54.13%	[]
vcard_emul_read_object	41	13	31.70%	[]

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
	[]	[]
/work/meson/../../src/libcacard/src/common.c	['fuzz_simpletlv', 'fuzz_xfer']	[]
/work/meson/../../src/libcacard/src/event.c	[]	[]
/work/meson/../../src/libcacard/src/cac-aca.c	[]	[]
/work/meson/../../src/libcacard/src/cac.c	[]	[]
/work/meson/../../src/libcacard/fuzz/fuzz_simpletlv.c	['fuzz_simpletlv']	[]
/work/meson/../../src/libcacard/src/vcard_emul_type.c	['fuzz_options']	[]
/work/meson/../../src/libcacard/fuzz/fuzz_xfer.c	['fuzz_xfer']	[]
/work/meson/../../src/libcacard/src/vcard.c	['fuzz_xfer']	[]
/work/meson/../../src/libcacard/src/vcardt.c	[]	[]
/work/meson/../../src/libcacard/src/card_7816.c	['fuzz_xfer']	[]
/work/meson/../../src/libcacard/src/vcard_emul_nss.c	['fuzz_options', 'fuzz_xfer']	[]
/work/meson/../../src/libcacard/src/vreader.c	['fuzz_xfer']	[]
/work/meson/../../src/libcacard/fuzz/fuzz_options.c	['fuzz_options']	[]
/work/meson/../../src/libcacard/src/gp.c	[]	[]
/work/meson/../../src/libcacard/src/msft.c	[]	[]
/work/meson/../../src/libcacard/src/simpletlv.c	['fuzz_simpletlv']	[]

Directories in report

Directory
/work/meson/../../src/libcacard/fuzz/
/work/meson/../../src/libcacard/src/