High level conclusions

Fuzzers reach 68.75% code coverage.

Fuzzers reach 65.46% of cyclomatic complexity.

Fuzzers reach 28.12% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

36 / 128

Cyclomatic complexity statically reachable by fuzzers

364 / 556

Runtime code coverage of functions

88 / 128

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

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	8.88%
gold	[1:9]	1	2.22%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	88.8%
All colors	45	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	1	LLVMFuzzerTestOneInput	call site: 00001	perror
1	15	usbredirfilter_string_to_rules	call site: 00015	usbredirfilter_verify
1	25	usbredirfilter_print	call site: 00025	fprintf

Runtime coverage analysis

Covered functions

9

Functions that are reachable but not covered

13

Reachable functions

20

Percentage of reachable functions covered

35.0%

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
/work/build/../../src/spice-usbredir/fuzzing/usbredirfilterfuzz.cc	1
/work/build/../../src/spice-usbredir/usbredirparser/usbredirfilter.c	6

Fuzzer: /work/build/meson-private/tmpghs7w8pk/testfile.cpp

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]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	1	100.%
All colors	1	100

Runtime coverage analysis

Covered functions

89

Functions that are reachable but not covered

0

Reachable functions

1

Percentage of reachable functions covered

100.0%

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
/work/build/meson-private/tmpghs7w8pk/testfile.cpp	1

Fuzzer: usbredirparserfuzz

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	19	8.83%
gold	[1:9]	6	2.79%
yellow	[10:29]	8	3.72%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	182	84.6%
All colors	215	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
4	94	usbredirparser_unserialize	call site: 00094	va_log
2	128	usbredirparser_unserialize	call site: 00128	va_log
2	140	usbredirparser_unserialize	call site: 00140	va_log
2	174	usbredirparser_do_read	call site: 00174	va_log
2	181	usbredirparser_do_read	call site: 00181	va_log
1	7	usbredirparser_verify_caps	call site: 00007	va_log
1	28	usbredirparser_get_type_header_len	call site: 00028	va_log
1	65	usbredirparser_verify_type_header	call site: 00065	va_log
1	67	usbredirparser_queue	call site: 00067	va_log
1	105	unserialize_data	call site: 00105	va_log
1	152	serialize_alloc	call site: 00152	va_log
1	213	usbredirparser_do_write	call site: 00213	abort

Runtime coverage analysis

Covered functions

84

Functions that are reachable but not covered

14

Reachable functions

49

Percentage of reachable functions covered

71.43%

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
/work/build/../../src/spice-usbredir/fuzzing/usbredirparserfuzz.cc	3
/work/build/../../src/spice-usbredir/usbredirparser/usbredirparser.c	28
/work/build/../../src/spice-usbredir/usbredirparser/usbredirfilter.c	2

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

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

Functions statically reachable by fuzzers

36 / 128

Cyclomatic complexity statically reachable by fuzzers

364 / 556

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.

/work/build/../../src/spice-usbredir/fuzzing/usbredirfilterfuzz.cc

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', 'usbredirfilter_string_to_rules', 'usbredirfilter_print']

/work/build/meson-private/tmpghs7w8pk/testfile.cpp

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

/work/build/../../src/spice-usbredir/fuzzing/usbredirparserfuzz.cc

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=['usbredirparser_unserialize', 'usbredirparser_do_read', 'usbredirparser_verify_caps', 'usbredirparser_get_type_header_len', 'usbredirparser_verify_type_header', 'usbredirparser_queue', 'unserialize_data']

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

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/build/../../src/spice-usbredir/usbredirparser/usbredirparser.c	['usbredirparserfuzz']	[]
/usr/local/bin/../include/c++/v1/stdexcept	[]	[]
/work/build/meson-private/tmpghs7w8pk/testfile.cpp	['/work/build/meson-private/tmpghs7w8pk/testfile.cpp']	['/work/build/meson-private/tmpghs7w8pk/testfile.cpp']
/work/build/../../src/spice-usbredir/usbredirparser/usbredirfilter.c	['usbredirfilterfuzz', 'usbredirparserfuzz']	[]
/work/build/../../src/spice-usbredir/fuzzing/usbredirfilterfuzz.cc	['usbredirfilterfuzz']	[]
/work/build/../../src/spice-usbredir/fuzzing/usbredirparserfuzz.cc	['usbredirparserfuzz']	[]

Directories in report

Directory
/work/build/meson-private/tmpghs7w8pk/
/work/build/../../src/spice-usbredir/fuzzing/
/usr/local/bin/../include/c++/v1/
/work/build/../../src/spice-usbredir/usbredirparser/