High level conclusions

Fuzzers reach 46.72% of cyclomatic complexity.

Fuzzers reach 44.40% of all functions.

Fuzzer fuzz_regex is blocked:

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

Fuzzer fuzz_search is blocked:

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

Fuzzer fuzz_match is blocked:

The runtime code coverage of fuzz_match covers 0.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

337/759

Cyclomatic complexity statically reachable by fuzzers

1150/2461

Runtime code coverage of functions

10 / 759

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_match

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	1069	98.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	12	1.11%
All colors	1081	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
1067	2	...fuzz_match.TestOneInput	call site: 00002	regex.regex._compile
2	1074	...fuzz_match.TestOneInput	call site: 01074	regex.regex._compile

Runtime coverage analysis

Covered functions

6

Functions that are reachable but not covered

363

Reachable functions

363

Percentage of reachable functions covered

0.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
/	1
...fuzz_match	5
regex.regex	51
regex._regex_core	326

Fuzzer: fuzz_search

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	1069	98.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	12	1.11%
All colors	1081	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
1067	2	...fuzz_search.TestOneInput	call site: 00002	regex.regex._compile
2	1074	...fuzz_search.TestOneInput	call site: 01074	regex.regex._compile

Runtime coverage analysis

Covered functions

6

Functions that are reachable but not covered

363

Reachable functions

363

Percentage of reachable functions covered

0.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
/	1
...fuzz_search	5
regex.regex	51
regex._regex_core	326

Fuzzer: fuzz_regex

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	1068	98.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	12	1.11%
All colors	1080	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
1066	4	...fuzz_regex.TestOneInput	call site: 00004	regex.regex._compile
2	1077	...fuzz_regex.TestOneInput	call site: 01077	regex.regex._compile

Runtime coverage analysis

Covered functions

6

Functions that are reachable but not covered

361

Reachable functions

361

Percentage of reachable functions covered

0.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
/	1
...fuzz_regex	5
regex.regex	50
regex._regex_core	325

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
regex.test_regex.RegexTests.test_hg_bugs	regex.test_regex	1	['N/A']	12	0	440	2	4	390	0	1320	80
regex.regex._compile_replacement_helper	regex.regex	2	['N/A', 'N/A']	3	0	7	8	6	36	0	129	47

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

Functions statically reachable by fuzzers

374/759

Cyclomatic complexity statically reachable by fuzzers

1277 / 2461

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

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
	[]	[]
...fuzz_regex	['fuzz_regex']	[]
pickle	[]	[]
copy	[]	[]
unicodedata	[]	[]
...fuzz_match	['fuzz_match']	[]
	[]	[]
collections	[]	[]
regex._regex	[]	[]
imp	[]	[]
unittest	[]	[]
threading	[]	[]
random	[]	[]
...fuzz_search	['fuzz_search']	[]
regex	[]	[]
regex.regex	['fuzz_match', 'fuzz_search', 'fuzz_regex']	[]
regex._regex_core	['fuzz_match', 'fuzz_search', 'fuzz_regex']	[]
array	[]	[]
pkg_resources	[]	[]
locale	[]	[]
weakref	[]	[]
regex.test_regex	[]	[]
atheris	[]	[]
copyreg	[]	[]

Directories in report

Directory

This section shows a chosen list of functions / methods calls and their relative coverage information. By static analysis of the target project code, all of these function call and their caller information, including the source file or class and line number that initiate the call are captured. Column 1 is the function name of that selected functions or methods. Column 2 of each row indicate if the target function covered by any fuzzer calltree information. Column 3 lists all fuzzers (or no fuzzers at all) that have coered that particular function call dynamically. Column 4 shows list of parent function for the specific function call, while column 5 shows possible blocker functions that make the fuzzers fail to reach the specific functions. Both column 4 and 5 will only show information if none of the fuzzers cover the target function calls.

Function in each files in report

Target sink	Callsite location	Reached by fuzzer	Function call path	Covered by fuzzer	Possible branch blockers