High level conclusions

Fuzzers reach 51.68% code coverage.

Fuzzers reach 45.10% of cyclomatic complexity.

Fuzzers reach 44.81% of all functions.

Fuzzer macho_fuzzer is blocked:

The runtime code coverage of macho_fuzzer covers 19.04% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer dex_fuzzer is blocked:

The runtime code coverage of dex_fuzzer covers 17.68% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer filemap_fuzzer is blocked:

The runtime code coverage of filemap_fuzzer covers 25.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Reachability and coverage overview

Functions statically reachable by fuzzers

359 / 801

Cyclomatic complexity statically reachable by fuzzers

3461 / 7674

Runtime code coverage of functions

414 / 801

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: tlsh_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	5	14.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	29	85.2%
All colors	34	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
1	5	tlsh_update	call site: 00005	fprintf
1	7	tlsh_impl_update	call site: 00007	raw_fast_update5_private
1	12	tlsh_final	call site: 00012	fprintf
1	21	tlsh_impl_hash	call site: 00021	strncpy
1	27	hash2	call site: 00027	to_hex

Runtime coverage analysis

Covered functions

21

Functions that are reachable but not covered

4

Reachable functions

25

Percentage of reachable functions covered

84.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
tests/oss-fuzz/tlsh_fuzzer.cc	1
libyara/tlshc/tlsh.c	6
libyara/tlshc/tlsh_impl.c	12
libyara/tlshc/tlsh_util.c	3

Fuzzer: filemap_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	2	12.5%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	14	87.5%
All colors	16	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	LLVMFuzzerTestOneInput	call site: 00002	close

Runtime coverage analysis

Covered functions

19

Functions that are reachable but not covered

9

Reachable functions

12

Percentage of reachable functions covered

25.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
tests/oss-fuzz/filemap_fuzzer.cc	1
libyara/filemap.c	2

Fuzzer: dex_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	529	91.5%
gold	[1:9]	25	4.32%
yellow	[10:29]	3	0.51%
greenyellow	[30:49]	2	0.34%
lawngreen	50+	19	3.28%
All colors	578	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
134	443	yr_modules_do_declarations	call site: 00443	yr_re_exec
101	221	yr_arena_create	call site: 00221	yr_hash_table_lookup
88	132	yr_hash_table_add_raw_key	call site: 00132	yr_scanner_scan_mem
84	358	_yr_arena_allocate_memory	call site: 00358	yr_modules_load
30	62	yr_object_create	call site: 00062	yr_object_set_integer
28	328	_yr_hash_table_lookup	call site: 00328	yr_object_dict_get_item
26	93	yr_realloc	call site: 00093	yr_object_set_string
12	6	yr_hash_table_create	call site: 00006	yr_scanner_destroy
9	37	yr_object_destroy	call site: 00037	yr_object_from_external_variable
4	30	yr_object_destroy	call site: 00030	yr_object_destroy
3	0	EP	call site: 00000	yr_rules_scan_mem
2	125	yr_hash_table_add_raw_key	call site: 00125	yr_free

Runtime coverage analysis

Covered functions

94

Functions that are reachable but not covered

121

Reachable functions

147

Percentage of reachable functions covered

17.69%

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
tests/oss-fuzz/dex_fuzzer.cc	2
libyara/rules.c	1
libyara/scanner.c	10
libyara/mem.c	5
libyara/hash.c	12
libyara/object.c	15
libyara/sizedstr.c	10
libyara/libyara.c	2
libyara/notebook.c	3
libyara/stopwatch.c	2
libyara/threading.c	2
libyara/exefiles.c	7
libyara/scan.c	14
libyara/strutils.c	1
libyara/exec.c	14
libyara/arena.c	7
./libyara/include/yara/unaligned.h	5
libyara/modules.c	3
libyara/re.c	11

Fuzzer: macho_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	526	91.0%
gold	[1:9]	29	5.01%
yellow	[10:29]	1	0.17%
greenyellow	[30:49]	1	0.17%
lawngreen	50+	21	3.63%
All colors	578	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
134	443	yr_modules_do_declarations	call site: 00443	yr_re_exec
101	221	yr_arena_create	call site: 00221	yr_hash_table_lookup
84	358	_yr_arena_allocate_memory	call site: 00358	yr_modules_load
78	142	yr_get_configuration_uint32	call site: 00142	yr_execute_code
30	62	yr_object_create	call site: 00062	yr_object_set_integer
26	93	yr_realloc	call site: 00093	yr_object_set_string
26	330	_yr_hash_table_lookup	call site: 00330	yr_object_dict_get_item
12	6	yr_hash_table_create	call site: 00006	yr_scanner_destroy
9	37	yr_object_destroy	call site: 00037	yr_object_from_external_variable
9	132	yr_hash_table_add_raw_key	call site: 00132	yr_scanner_scan_mem
4	30	yr_object_destroy	call site: 00030	yr_object_destroy
3	0	EP	call site: 00000	yr_rules_scan_mem

Runtime coverage analysis

Covered functions

108

Functions that are reachable but not covered

119

Reachable functions

147

Percentage of reachable functions covered

19.05%

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
tests/oss-fuzz/macho_fuzzer.cc	2
libyara/rules.c	1
libyara/scanner.c	10
libyara/mem.c	5
libyara/hash.c	12
libyara/object.c	15
libyara/sizedstr.c	10
libyara/libyara.c	2
libyara/notebook.c	3
libyara/stopwatch.c	2
libyara/threading.c	2
libyara/exefiles.c	7
libyara/scan.c	14
libyara/strutils.c	1
libyara/exec.c	14
libyara/arena.c	7
./libyara/include/yara/unaligned.h	5
libyara/modules.c	3
libyara/re.c	11

Fuzzer: elf_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	408	70.5%
gold	[1:9]	8	1.38%
yellow	[10:29]	2	0.34%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	160	27.6%
All colors	578	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
113	447	yr_modules_load	call site: 00447	yr_re_exec
94	228	yr_execute_code	call site: 00228	yr_hash_table_lookup
76	358	_yr_arena_allocate_memory	call site: 00358	read_int8_t_little_endian
41	168	yr_scanner_scan_mem_blocks	call site: 00168	yr_scan_verify_match
23	333	_yr_hash_table_lookup	call site: 00333	yr_object_dict_get_item
13	93	yr_realloc	call site: 00093	yr_object_dict_get_item
5	82	yr_object_copy	call site: 00082	yr_object_copy
5	107	yr_object_set_integer	call site: 00107	yr_object_set_string
4	30	yr_object_destroy	call site: 00030	yr_object_destroy
4	73	yr_object_copy	call site: 00073	yr_object_copy
3	14	yr_scanner_create	call site: 00014	yr_scanner_destroy
3	116	yr_object_set_string	call site: 00116	yr_scanner_destroy

Runtime coverage analysis

Covered functions

142

Functions that are reachable but not covered

81

Reachable functions

147

Percentage of reachable functions covered

44.9%

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
tests/oss-fuzz/elf_fuzzer.cc	2
libyara/rules.c	1
libyara/scanner.c	10
libyara/mem.c	5
libyara/hash.c	12
libyara/object.c	15
libyara/sizedstr.c	10
libyara/libyara.c	2
libyara/notebook.c	3
libyara/stopwatch.c	2
libyara/threading.c	2
libyara/exefiles.c	7
libyara/scan.c	14
libyara/strutils.c	1
libyara/exec.c	14
libyara/arena.c	7
./libyara/include/yara/unaligned.h	5
libyara/modules.c	3
libyara/re.c	11

Fuzzer: math_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	393	67.9%
gold	[1:9]	4	0.69%
yellow	[10:29]	3	0.51%
greenyellow	[30:49]	2	0.34%
lawngreen	50+	176	30.4%
All colors	578	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
76	358	_yr_arena_allocate_memory	call site: 00358	read_int8_t_little_endian
49	447	yr_modules_load	call site: 00447	yr_re_exec
41	168	yr_scanner_scan_mem_blocks	call site: 00168	yr_scan_verify_match
33	527	yr_execute_code	call site: 00527	ss_compare
24	228	yr_execute_code	call site: 00228	yr_notebook_alloc
19	73	yr_object_copy	call site: 00073	yr_object_copy
19	292	yr_execute_code	call site: 00292	yr_arena_ptr_to_ref
16	253	yr_execute_code	call site: 00253	jmp_if
15	510	yr_execute_code	call site: 00510	__assert_fail
13	93	yr_realloc	call site: 00093	yr_object_dict_get_item
12	270	jmp_if	call site: 00270	jmp_if
11	497	yr_execute_code	call site: 00497	__assert_fail

Runtime coverage analysis

Covered functions

165

Functions that are reachable but not covered

80

Reachable functions

147

Percentage of reachable functions covered

45.58%

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
tests/oss-fuzz/math_fuzzer.cc	2
libyara/rules.c	1
libyara/scanner.c	10
libyara/mem.c	5
libyara/hash.c	12
libyara/object.c	15
libyara/sizedstr.c	10
libyara/libyara.c	2
libyara/notebook.c	3
libyara/stopwatch.c	2
libyara/threading.c	2
libyara/exefiles.c	7
libyara/scan.c	14
libyara/strutils.c	1
libyara/exec.c	14
libyara/arena.c	7
./libyara/include/yara/unaligned.h	5
libyara/modules.c	3
libyara/re.c	11

Fuzzer: dotnet_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	384	66.4%
gold	[1:9]	7	1.21%
yellow	[10:29]	3	0.51%
greenyellow	[30:49]	1	0.17%
lawngreen	50+	183	31.6%
All colors	578	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
93	447	yr_modules_load	call site: 00447	yr_re_exec
76	358	_yr_arena_allocate_memory	call site: 00358	read_int8_t_little_endian
58	253	yr_execute_code	call site: 00253	yr_arena_ptr_to_ref
41	168	yr_scanner_scan_mem_blocks	call site: 00168	yr_scan_verify_match
24	228	yr_execute_code	call site: 00228	yr_notebook_alloc
17	339	yr_execute_code	call site: 00339	yr_object_dict_get_item
17	543	yr_execute_code	call site: 00543	ss_compare
13	93	yr_realloc	call site: 00093	yr_object_dict_get_item
5	30	yr_object_destroy	call site: 00030	yr_object_destroy
5	107	yr_object_set_integer	call site: 00107	yr_object_set_string
4	73	yr_object_copy	call site: 00073	yr_object_copy
3	14	yr_scanner_create	call site: 00014	yr_scanner_destroy

Runtime coverage analysis

Covered functions

202

Functions that are reachable but not covered

76

Reachable functions

147

Percentage of reachable functions covered

48.3%

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
tests/oss-fuzz/dotnet_fuzzer.cc	2
libyara/rules.c	1
libyara/scanner.c	10
libyara/mem.c	5
libyara/hash.c	12
libyara/object.c	15
libyara/sizedstr.c	10
libyara/libyara.c	2
libyara/notebook.c	3
libyara/stopwatch.c	2
libyara/threading.c	2
libyara/exefiles.c	7
libyara/scan.c	14
libyara/strutils.c	1
libyara/exec.c	14
libyara/arena.c	7
./libyara/include/yara/unaligned.h	5
libyara/modules.c	3
libyara/re.c	11

Fuzzer: pe_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	356	61.5%
gold	[1:9]	5	0.86%
yellow	[10:29]	5	0.86%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	212	36.6%
All colors	578	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
83	228	yr_execute_code	call site: 00228	yr_notebook_alloc
76	358	_yr_arena_allocate_memory	call site: 00358	read_int8_t_little_endian
60	500	yr_execute_code	call site: 00500	ss_compare
51	447	yr_modules_load	call site: 00447	yr_re_exec
41	168	yr_scanner_scan_mem_blocks	call site: 00168	yr_scan_verify_match
5	107	yr_object_set_integer	call site: 00107	yr_object_set_string
4	73	yr_object_copy	call site: 00073	yr_object_copy
4	344	yr_execute_code	call site: 00344	yr_object_dict_get_item
3	14	yr_scanner_create	call site: 00014	yr_scanner_destroy
3	84	yr_object_copy	call site: 00084	yr_object_copy
3	116	yr_object_set_string	call site: 00116	yr_scanner_destroy
3	132	yr_hash_table_add_raw_key	call site: 00132	yr_scanner_destroy

Runtime coverage analysis

Covered functions

192

Functions that are reachable but not covered

75

Reachable functions

147

Percentage of reachable functions covered

48.98%

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
tests/oss-fuzz/pe_fuzzer.cc	2
libyara/rules.c	1
libyara/scanner.c	10
libyara/mem.c	5
libyara/hash.c	12
libyara/object.c	15
libyara/sizedstr.c	10
libyara/libyara.c	2
libyara/notebook.c	3
libyara/stopwatch.c	2
libyara/threading.c	2
libyara/exefiles.c	7
libyara/scan.c	14
libyara/strutils.c	1
libyara/exec.c	14
libyara/arena.c	7
./libyara/include/yara/unaligned.h	5
libyara/modules.c	3
libyara/re.c	11

Fuzzer: rules_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	934	53.8%
gold	[1:9]	11	0.63%
yellow	[10:29]	9	0.51%
greenyellow	[30:49]	7	0.40%
lawngreen	50+	774	44.6%
All colors	1735	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
107	700	re_yyrestart	call site: 00700	read_escaped_char
101	216	yara_yypop_buffer_state	call site: 00216	yr_parser_reduce_import
59	1280	yr_parser_reduce_string_identifier	call site: 01280	yara_yyerror
52	1216	yr_parser_emit_push_const	call site: 01216	yara_yyerror
36	115	yara_yy_scan_bytes	call site: 00115	yara_yyerror
36	530	xtoi	call site: 00530	yy_get_next_buffer
35	178	yara_yylex	call site: 00178	yara_yy_scan_string
34	567	yr_re_node_create	call site: 00567	hex_yyerror
32	1164	yr_parser_check_types	call site: 01164	yr_re_compile
29	1083	yr_parser_reduce_string_declaration	call site: 01083	yr_parser_reduce_string_declaration
26	1127	yr_parser_lookup_loop_variable	call site: 01127	yara_yyerror
18	1340	yr_string_set_destroy	call site: 01340	yara_yyerror

Runtime coverage analysis

Covered functions

252

Functions that are reachable but not covered

52

Reachable functions

275

Percentage of reachable functions covered

81.09%

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
tests/oss-fuzz/rules_fuzzer.cc	1
libyara/compiler.c	15
libyara/mem.c	5
libyara/hash.c	15
libyara/arena.c	14
libyara/ahocorasick.c	15
libyara/object.c	4
libyara/lexer.l	5
libyara/lexer.c	27
libyara/strutils.c	3
libyara/libyara.c	2
libyara/grammar.c	6
libyara/parser.c	24
libyara/modules.c	1
libyara/re.c	21
libyara/hex_lexer.l	3
libyara/threading.c	2
libyara/hex_lexer.c	24
hex_grammar.c	2
libyara/re_lexer.l	6
libyara/re_lexer.c	25
re_grammar.c	2
libyara/base64.c	7
libyara/sizedstr.c	3
libyara/atoms.c	17
libyara/stack.c	4
libyara/bitmask.c	1
libyara/rules.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
dotnet__load	/src/yara/libyara/modules/dotnet/dotnet.c	4	['N/A', 'N/A', 'N/A', 'size_t']	13	0	148	21	8	86	0	806	649
pe__declarations	/src/yara/libyara/modules/pe/pe.c	1	['N/A']	8	0	6511	772	330	86	0	895	585
pe__load	/src/yara/libyara/modules/pe/pe.c	4	['N/A', 'N/A', 'N/A', 'size_t']	10	0	541	23	9	69	0	634	444
elf__load	/src/yara/libyara/modules/elf/elf.c	4	['N/A', 'N/A', 'N/A', 'size_t']	8	0	545	56	21	42	0	447	302
macho__declarations	/src/yara/libyara/modules/macho/macho.c	1	['N/A']	8	0	4385	520	239	34	0	408	262
math__declarations	/src/yara/libyara/modules/math/math.c	1	['N/A']	8	0	459	52	26	62	0	376	212
elf__declarations	/src/yara/libyara/modules/elf/elf.c	1	['N/A']	8	0	2849	339	152	60	0	482	202
dex__declarations	/src/yara/libyara/modules/dex/dex.c	1	['N/A']	8	0	3343	401	155	52	0	499	195
dex__load	/src/yara/libyara/modules/dex/dex.c	4	['N/A', 'N/A', 'N/A', 'size_t']	10	0	215	15	6	41	0	300	147
macho__load	/src/yara/libyara/modules/macho/macho.c	4	['N/A', 'N/A', 'N/A', 'size_t']	9	0	116	17	7	55	0	263	114

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

Functions statically reachable by fuzzers

566 / 801

Cyclomatic complexity statically reachable by fuzzers

6553 / 7674

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.

tests/oss-fuzz/tlsh_fuzzer.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=['tlsh_update', 'tlsh_impl_update', 'tlsh_final', 'tlsh_impl_hash', 'hash2']

tests/oss-fuzz/filemap_fuzzer.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']

tests/oss-fuzz/dex_fuzzer.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=['yr_modules_do_declarations', 'yr_arena_create', 'yr_hash_table_add_raw_key', '_yr_arena_allocate_memory', 'yr_object_create', '_yr_hash_table_lookup', 'yr_realloc', 'yr_hash_table_create', 'yr_object_destroy']

tests/oss-fuzz/macho_fuzzer.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=['yr_modules_do_declarations', 'yr_arena_create', '_yr_arena_allocate_memory', 'yr_get_configuration_uint32', 'yr_object_create', 'yr_realloc', '_yr_hash_table_lookup', 'yr_hash_table_create', 'yr_object_destroy', 'yr_hash_table_add_raw_key']

tests/oss-fuzz/elf_fuzzer.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=['yr_modules_load', 'yr_execute_code', '_yr_arena_allocate_memory', 'yr_scanner_scan_mem_blocks', '_yr_hash_table_lookup', 'yr_realloc', 'yr_object_copy', 'yr_object_set_integer', 'yr_object_destroy']

tests/oss-fuzz/math_fuzzer.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=['_yr_arena_allocate_memory', 'yr_modules_load', 'yr_scanner_scan_mem_blocks', 'yr_execute_code', 'yr_object_copy', 'yr_realloc']

tests/oss-fuzz/dotnet_fuzzer.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=['yr_modules_load', '_yr_arena_allocate_memory', 'yr_execute_code', 'yr_scanner_scan_mem_blocks', 'yr_realloc', 'yr_object_destroy', 'yr_object_set_integer']

tests/oss-fuzz/pe_fuzzer.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=['yr_execute_code', '_yr_arena_allocate_memory', 'yr_modules_load', 'yr_scanner_scan_mem_blocks', 'yr_object_set_integer', 'yr_object_copy', 'yr_scanner_create']

tests/oss-fuzz/rules_fuzzer.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=['re_yyrestart', 'yara_yypop_buffer_state', 'yr_parser_reduce_string_identifier', 'yr_parser_emit_push_const', 'yara_yy_scan_bytes', 'xtoi', 'yara_yylex', 'yr_re_node_create', 'yr_parser_check_types', 'yr_parser_reduce_string_declaration']

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
tlsh_impl_update	118	21	17.79%	['tlsh_fuzzer']
yydestruct	67	5	7.462%	['elf_fuzzer', 'dex_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'math_fuzzer', 'macho_fuzzer', 'rules_fuzzer']
yr_execute_code	1563	349	22.32%	['elf_fuzzer', 'dex_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'math_fuzzer', 'macho_fuzzer']
_yr_scanner_scan_mem_block	117	49	41.88%	['elf_fuzzer', 'dex_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'math_fuzzer', 'macho_fuzzer']
_yr_compiler_default_include_callback	41	17	41.46%	['rules_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/yara/libyara/hex_lexer.c	['rules_fuzzer']	['rules_fuzzer']
/src/yara/libyara/arena.c	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'rules_fuzzer']	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'rules_fuzzer']
/src/yara/libyara/notebook.c	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer']	['elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer']
/src/yara/tests/oss-fuzz/dex_fuzzer.cc	['dex_fuzzer']	['dex_fuzzer']
/src/yara/tests/oss-fuzz/elf_fuzzer.cc	['elf_fuzzer']	['elf_fuzzer']
/src/yara/libyara/atoms.c	['rules_fuzzer']	['rules_fuzzer']
/src/yara/libyara/tlshc/tlsh.c	['tlsh_fuzzer']	['tlsh_fuzzer']
/src/yara/libyara/modules.c	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'rules_fuzzer']	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'rules_fuzzer']
/src/yara/libyara/modules/pe/pe.c	[]	[]
/src/yara/tests/oss-fuzz/pe_fuzzer.cc	['pe_fuzzer']	['pe_fuzzer']
/src/yara/tests/oss-fuzz/math_fuzzer.cc	['math_fuzzer']	['math_fuzzer']
/src/yara/./libyara/include/yara/unaligned.h	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer']	[]
/src/yara/libyara/proc.c	[]	[]
/src/yara/libyara/re_lexer.l	['rules_fuzzer']	['rules_fuzzer']
/src/yara/libyara/grammar.c	['rules_fuzzer']	['rules_fuzzer']
/src/yara/libyara/libyara.c	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'rules_fuzzer']	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'rules_fuzzer']
/src/yara/libyara/exefiles.c	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer']	['elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer']
/src/yara/libyara/parser.c	['rules_fuzzer']	['rules_fuzzer']
/src/yara/libyara/bitmask.c	['rules_fuzzer']	['rules_fuzzer']
/src/yara/libyara/modules/elf/elf.c	[]	[]
/src/yara/libyara/lexer.l	['rules_fuzzer']	['rules_fuzzer']
/src/yara/libyara/modules/tests/tests.c	[]	[]
/src/yara/re_grammar.c	['rules_fuzzer']	['rules_fuzzer']
/src/yara/tests/oss-fuzz/tlsh_fuzzer.cc	['tlsh_fuzzer']	['tlsh_fuzzer']
/src/yara/libyara/mem.c	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'rules_fuzzer']	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'rules_fuzzer']
/src/yara/libyara/rules.c	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'rules_fuzzer']	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'rules_fuzzer']
/src/yara/libyara/simple_str.c	[]	[]
/src/yara/libyara/modules/pe/pe_utils.c	[]	[]
/src/yara/libyara/re_lexer.c	['rules_fuzzer']	['rules_fuzzer']
/src/yara/libyara/scan.c	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer']	[]
/src/yara/libyara/modules/string/string.c	[]	[]
/src/yara/libyara/hash.c	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'rules_fuzzer']	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'rules_fuzzer']
/src/yara/libyara/exception.h	[]	[]
/src/yara/tests/oss-fuzz/macho_fuzzer.cc	['macho_fuzzer']	['macho_fuzzer']
/src/yara/libyara/lexer.c	['rules_fuzzer']	['rules_fuzzer']
/src/yara/libyara/modules/macho/macho.c	[]	[]
/src/yara/libyara/exec.c	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer']	['elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer']
/src/yara/hex_grammar.c	['rules_fuzzer']	['rules_fuzzer']
/src/yara/libyara/modules/math/math.c	[]	[]
/src/yara/libyara/stopwatch.c	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer']	['elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer']
/src/yara/libyara/tlshc/tlsh_impl.c	['tlsh_fuzzer']	['tlsh_fuzzer']
/src/yara/libyara/compiler.c	['rules_fuzzer']	['rules_fuzzer']
/src/yara/libyara/object.c	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'rules_fuzzer']	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'rules_fuzzer']
/src/yara/libyara/filemap.c	['filemap_fuzzer']	['filemap_fuzzer']
/src/yara/libyara/tlshc/tlsh_util.c	['tlsh_fuzzer']	['tlsh_fuzzer']
/src/yara/libyara/modules/console/console.c	[]	[]
/src/yara/libyara/scanner.c	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer']	['elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer']
/src/yara/libyara/strutils.c	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'rules_fuzzer']	['math_fuzzer', 'pe_fuzzer', 'rules_fuzzer']
/src/yara/libyara/modules/time/time.c	[]	[]
/src/yara/libyara/threading.c	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'rules_fuzzer']	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'rules_fuzzer']
/src/yara/tests/oss-fuzz/rules_fuzzer.cc	['rules_fuzzer']	['rules_fuzzer']
/src/yara/libyara/sizedstr.c	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'rules_fuzzer']	['dotnet_fuzzer', 'pe_fuzzer', 'rules_fuzzer']
/src/yara/libyara/stack.c	['rules_fuzzer']	['rules_fuzzer']
/src/yara/tests/oss-fuzz/dotnet_fuzzer.cc	['dotnet_fuzzer']	['dotnet_fuzzer']
/src/yara/tests/oss-fuzz/filemap_fuzzer.cc	['filemap_fuzzer']	['filemap_fuzzer']
/src/yara/libyara/modules/dex/dex.c	[]	[]
/src/yara/libyara/modules/dotnet/dotnet.c	[]	[]
/src/yara/libyara/stream.c	[]	[]
/src/yara/./libyara/include/yara/utils.h	[]	[]
/src/yara/libyara/re.c	['dex_fuzzer', 'macho_fuzzer', 'elf_fuzzer', 'math_fuzzer', 'dotnet_fuzzer', 'pe_fuzzer', 'rules_fuzzer']	['rules_fuzzer']
/src/yara/libyara/ahocorasick.c	['rules_fuzzer']	['rules_fuzzer']
/src/yara/libyara/base64.c	['rules_fuzzer']	['rules_fuzzer']
/src/yara/libyara/proc/linux.c	[]	[]
/src/yara/libyara/hex_lexer.l	['rules_fuzzer']	['rules_fuzzer']

Directories in report

Directory
/src/yara/libyara/modules/pe/
/src/yara/libyara/
/src/yara/libyara/tlshc/
/src/yara/
/src/yara/libyara/modules/string/
/src/yara/libyara/modules/macho/
/src/yara/libyara/proc/
/src/yara/libyara/modules/dex/
/src/yara/libyara/modules/math/
/src/yara/libyara/modules/elf/
/src/yara/libyara/modules/console/
/src/yara/libyara/modules/tests/
/src/yara/./libyara/include/yara/
/src/yara/libyara/modules/time/
/src/yara/tests/oss-fuzz/
/src/yara/libyara/modules/dotnet/