High level conclusions

Fuzzers reach 51.31% code coverage.

Fuzzers reach 1.812% of cyclomatic complexity.

Fuzzers reach 2.192% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

5 / 228

Cyclomatic complexity statically reachable by fuzzers

6 / 331

Runtime code coverage of functions

117 / 228

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

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	98	87.5%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	2	1.78%
lawngreen	50+	12	10.7%
All colors	112	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
30	14	my_hash	call site: 00014	fuzz_target
27	50	is_combining_mark	call site: 00050	decompose
26	85	canonical_fully_decomposed	call site: 00085	decompose
11	0	EP	call site: 00000	Replacements::next
2	46	canonical_combining_class	call site: 00046	Replacements::next
2	80	compatibility_fully_decomposed	call site: 00080

Runtime coverage analysis

Covered functions

129

Functions that are reachable but not covered

12

Reachable functions

22

Percentage of reachable functions covered

45.45%

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
unicode-normalization/fuzz/fuzz_targets/process.rs	18
unicode-normalizationreplace.rs	7
unicode-normalizationnormalize.rs	10
unicode-normalizationlookups.rs	3
unicode-normalizationperfect_hash.rs	7
unicode-normalization/fuzz/fuzz_targets/streaming.rs	17
unicode-normalization__test_api.rs	3

Fuzzer: unicode-normalization

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

Runtime coverage analysis

Covered functions

245

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.

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
unicode-normalization/fuzz/fuzz_targets/unicode-normalization.rs	14
unicode-normalization__test_api.rs	3

Fuzzer: streaming

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	13	100.%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	0	0.0%
All colors	13	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
12	0	EP	call site: 00000

Runtime coverage analysis

Covered functions

245

Functions that are reachable but not covered

7

Reachable functions

12

Percentage of reachable functions covered

41.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
unicode-normalization/fuzz/fuzz_targets/streaming.rs	9
unicode-normalization__test_api.rs	3

Fuzzer: fuzz_target_1

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	57	87.6%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	8	12.3%
All colors	65	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
38	19	new_graphemes	call site: 00019
16	0	EP	call site: 00000	test_graphemes
3	61	word::new_unicode_words	call site: 00061

Runtime coverage analysis

Covered functions

245

Functions that are reachable but not covered

5

Reachable functions

8

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.

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
unicode-segmentation/fuzz/fuzz_targets/fuzz_target_1.rs	8
unicode-segmentation/tests/test.rs	12
unicode-segmentationgrapheme.rs	4
unicode-normalizationreplace.rs	1
unicode-segmentationlib.rs	2
unicode-segmentationword.rs	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

5 / 228

Cyclomatic complexity statically reachable by fuzzers

6 / 331

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.

unicode-normalization/fuzz/fuzz_targets/process.rs

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=['my_hash', 'is_combining_mark', 'canonical_fully_decomposed', 'canonical_combining_class', 'compatibility_fully_decomposed']

unicode-normalization/fuzz/fuzz_targets/unicode-normalization.rs

Dictionary

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

unicode-normalization/fuzz/fuzz_targets/streaming.rs

Dictionary

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

unicode-segmentation/fuzz/fuzz_targets/fuzz_target_1.rs

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=['new_graphemes', 'word::new_unicode_words']

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

New fuzzers

The below fuzzers are templates and suggestions for how to target the set of optimal functions above

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/unicode-normalization/tests/test_streamsafe_regression.rs	[]	[]
/src/unicode-segmentation/src/tables.rs	[]	[]
/src/unicode-normalization/tests/cjk_compat_variants.rs	[]	[]
/src/unicode-normalization/src/tables.rs	[]	[]
/src/unicode-normalization/src/__test_api.rs	['process', 'unicode-normalization', 'streaming']	['process', 'unicode-normalization', 'streaming']
/src/unicode-normalization/src/test.rs	[]	[]
/src/unicode-normalization/src/perfect_hash.rs	['process']	['process']
/src/unicode-segmentation/src/sentence.rs	[]	[]
/src/unicode-segmentation/fuzz/fuzz_targets/fuzz_target_1.rs	['fuzz_target_1']	[]
/src/unicode-normalization/src/stream_safe.rs	[]	[]
/src/unicode-normalization/src/decompose.rs	[]	[]
/src/unicode-normalization/fuzz/fuzz_targets/streaming.rs	['process', 'streaming']	['process', 'streaming']
/src/unicode-segmentation/benches/words.rs	[]	[]
/src/unicode-normalization/benches/bench.rs	[]	[]
/src/unicode-normalization/tests/tests.rs	[]	[]
/src/unicode-normalization/src/replace.rs	['process', 'fuzz_target_1']	['process', 'fuzz_target_1']
/src/unicode-segmentation/src/grapheme.rs	['fuzz_target_1']	['fuzz_target_1']
/src/unicode-normalization/tests/public_assigned.rs	[]	[]
/src/unicode-normalization/fuzz/fuzz_targets/process.rs	['process']	[]
/src/unicode-segmentation/src/lib.rs	['fuzz_target_1']	['fuzz_target_1']
/src/unicode-normalization/fuzz/fuzz_targets/unicode-normalization.rs	['unicode-normalization']	['unicode-normalization']
/src/unicode-normalization/src/lib.rs	[]	[]
/src/unicode-segmentation/src/word.rs	['fuzz_target_1']	['fuzz_target_1']
/src/unicode-normalization/src/lookups.rs	['process']	['process']
/src/unicode-normalization/src/recompose.rs	[]	[]
/src/unicode-normalization/src/normalize.rs	['process']	['process']
/src/unicode-normalization/src/quick_check.rs	[]	[]
/src/unicode-segmentation/tests/test.rs	['fuzz_target_1']	[]

Directories in report

Directory
/src/unicode-segmentation/src/
/src/unicode-segmentation/fuzz/fuzz_targets/
/src/unicode-segmentation/tests/
/src/unicode-normalization/fuzz/fuzz_targets/
/src/unicode-segmentation/benches/
/src/unicode-normalization/src/
/src/unicode-normalization/tests/
/src/unicode-normalization/benches/

This section shows a list of 3rd party function calls and their relative coverage information. By static analysis of the target project code, all of the 3rd party function call and their caller information, including the source file and line number that initiate the call are captured. The caller source code file and line number are shown in column 2 while column 1 is the function name of the 3rd party function call. Each occurrent of the 3rd party function call will occuply a separate row. Column 3 of each row indicate if the 3rd party call in the source file line is unreachable. Column 4 lists all fuzzers that have covered that particular system call in that specific location (source file and line)during their dynamic fuzzing.

Function in each files in report

Target sink	Callsite location	Reached by fuzzer	Covered by Fuzzers