High level conclusions

Fuzzers reach 50.76% code coverage.

Fuzzer fuzz_config is blocked:

The runtime code coverage of fuzz_config covers 2.046% 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_repo is blocked:

The runtime code coverage of fuzz_repo covers 2.564% 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_submodule is blocked:

The runtime code coverage of fuzz_submodule 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_blob is blocked:

The runtime code coverage of fuzz_blob covers 5.454% 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_diff is blocked:

The runtime code coverage of fuzz_diff covers 4.385% 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

62 / 656

Cyclomatic complexity statically reachable by fuzzers

265 / 2314

Runtime code coverage of functions

333 / 656

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

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	219	74.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	75	25.5%
All colors	294	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
154	56	...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput	call site: 00056	git.diff.Diff._index_from_patch_format
25	243	git.util.finalize_process	call site: 00243	git.diff.Diff.__init__
24	269	...gitpython.fuzzing.fuzz-targets.fuzz_diff.BytesProcessAdapter.__init__	call site: 00269	git.diff.Diff._handle_diff_line
7	37	git.objects.base.IndexObject.__init__	call site: 00037	git.objects.base.IndexObject.__init__
5	47	...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput	call site: 00047	fdp.ConsumeBytes
3	31	git.diff.Diff.__init__	call site: 00031	a_rawpath.decode
1	22	...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput	call site: 00022	git.diff.Diff.__init__

Runtime coverage analysis

Covered functions

389

Functions that are reachable but not covered

218

Reachable functions

228

Percentage of reachable functions covered

4.39%

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
/	1
...gitpython.fuzzing.fuzz-targets.fuzz_diff	34
git.diff	40
git.objects.util	4
git.objects.base	1
git.cmd	77
git.util	79

Fuzzer: fuzz_blob

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	894	76.9%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	268	23.0%
All colors	1162	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
351	468	git.repo.fun.rev_parse	call site: 00468	git.repo.base.Repo.__init__
85	73	git.util.is_cygwin_git	call site: 00073	git.util._is_cygwin_git
68	906	git.config.GitConfigParser.__init__	call site: 00906	git.repo.base.Repo.__init__
66	1088	git.repo.base.Repo.__init__	call site: 01088	git.repo.base.Repo.__init__
61	284	git.repo.fun.name_to_object	call site: 00284	git.repo.fun.short_to_long
57	845	git.repo.base.Repo._get_config_path	call site: 00845	git.repo.base.Repo.__init__
55	412	git.repo.fun.name_to_object	call site: 00412	git.repo.base.Repo.__init__
52	5	git.util.expand_path	call site: 00005	typing.BinaryIO.object.head.commit.tree.resolve
44	184	git.repo.base.Repo.__init__	call site: 00184	git.repo.fun.rev_parse
15	820	git.repo.fun.rev_parse	call site: 00820	git.repo.base.Repo._get_config_path
13	397	git.repo.fun.name_to_object	call site: 00397	git.remote.PushInfoList.__init__
6	175	git.repo.fun.is_git_dir	call site: 00175	os.path.join

Runtime coverage analysis

Covered functions

389

Functions that are reachable but not covered

468

Reachable functions

495

Percentage of reachable functions covered

5.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.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/	1
...gitpython.fuzzing.fuzz-targets.fuzz_blob	9
git.repo.base	100
git.util	138
git.cmd	3
git.repo.fun	314
git.remote	1
git.config	69
git.db	1

Fuzzer: fuzz_submodule

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	47	29.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	111	70.2%
All colors	158	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
44	113	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.TestOneInput	call site: 00113	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.sanitize_input
3	103	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.TestOneInput	call site: 00103	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.sanitize_input

Runtime coverage analysis

Covered functions

388

Functions that are reachable but not covered

81

Reachable functions

81

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.

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
/	1
...gitpython.fuzzing.fuzz-targets.fuzz_submodule	80

Fuzzer: fuzz_repo

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	3.12%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	155	96.8%
All colors	160	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	69	...gitpython.fuzzing.fuzz-targets.fuzz_repo.TestOneInput	call site: 00069	os.path.join
1	0	EP	call site: 00000	atheris.FuzzedDataProvider

Runtime coverage analysis

Covered functions

389

Functions that are reachable but not covered

152

Reachable functions

156

Percentage of reachable functions covered

2.56%

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
/	1
...gitpython.fuzzing.fuzz-targets.fuzz_repo	81
git.objects.tree	2
git.objects.fun	4
git.compat	68

Fuzzer: fuzz_config

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	141	23.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	464	76.6%
All colors	605	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
126	473	git.config.GitConfigParser.read	call site: 00473	typing.IO.tree
13	455	git.config.GitConfigParser._included_paths	call site: 00455	git.config.GitConfigParser.items
1	1	...gitpython.fuzzing.fuzz-targets.fuzz_config.TestOneInput	call site: 00001	git.config.GitConfigParser.read
1	603	git.config.GitConfigParser.read	call site: 00603	.str

Runtime coverage analysis

Covered functions

388

Functions that are reachable but not covered

335

Reachable functions

342

Percentage of reachable functions covered

2.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.

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
/	1
...gitpython.fuzzing.fuzz-targets.fuzz_config	3
git.config	339

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
git.objects.submodule.root.RootModule.update	git.objects.submodule.root	10	['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A']	5	0	20	24	13	571	0	1743	1515

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

Functions statically reachable by fuzzers

86 / 656

Cyclomatic complexity statically reachable by fuzzers

364 / 2314

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.

/src/gitpython/fuzzing/fuzz-targets/fuzz_diff.py

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=['...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput', 'git.util.finalize_process', '...gitpython.fuzzing.fuzz-targets.fuzz_diff.BytesProcessAdapter.__init__', 'git.objects.base.IndexObject.__init__', 'git.diff.Diff.__init__']

/src/gitpython/fuzzing/fuzz-targets/fuzz_blob.py

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=['git.repo.fun.rev_parse', 'git.util.is_cygwin_git', 'git.config.GitConfigParser.__init__', 'git.repo.base.Repo.__init__', 'git.repo.fun.name_to_object', 'git.repo.base.Repo._get_config_path', 'git.util.expand_path']

/src/gitpython/fuzzing/fuzz-targets/fuzz_submodule.py

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=['...gitpython.fuzzing.fuzz-targets.fuzz_submodule.TestOneInput']

/src/gitpython/fuzzing/fuzz-targets/fuzz_repo.py

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=['...gitpython.fuzzing.fuzz-targets.fuzz_repo.TestOneInput']

/src/gitpython/fuzzing/fuzz-targets/fuzz_config.py

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=['git.config.GitConfigParser.read', 'git.config.GitConfigParser._included_paths', '...gitpython.fuzzing.fuzz-targets.fuzz_config.TestOneInput']

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
git.diff.Diffable.diff	39	5	12.82%	['fuzz_diff', 'fuzz_blob', 'fuzz_config', 'fuzz_repo', 'fuzz_submodule']
git.diff.Diff.__str__	33	0	0.0%	['fuzz_diff']
git.diff.Diff._handle_diff_line	39	0	0.0%	['fuzz_diff']
git.objects.submodule	39	20	51.28%	['fuzz_repo', 'fuzz_diff', 'fuzz_blob', 'fuzz_submodule']
git.cmd.handle_process_output.pump_stream	51	2	3.921%	['fuzz_diff', 'fuzz_blob', 'fuzz_config', 'fuzz_repo', 'fuzz_submodule']
git.cmd.Git.refresh	35	12	34.28%	['fuzz_diff', 'fuzz_blob', 'fuzz_config', 'fuzz_repo', 'fuzz_submodule']
git.cmd.Git.execute.communicate	34	16	47.05%	['fuzz_diff', 'fuzz_blob', 'fuzz_config', 'fuzz_repo', 'fuzz_submodule']
git.remote.PushInfo._from_line	32	0	0.0%	[]
git.remote.FetchInfo._from_line	56	0	0.0%	[]
git.remote.Remote._get_fetch_info_from_stderr	39	0	0.0%	[]
git.index.base.IndexFile.checkout.handle_stderr	49	0	0.0%	[]
git.objects.util.parse_date	46	2	4.347%	['fuzz_diff', 'fuzz_blob', 'fuzz_config', 'fuzz_repo', 'fuzz_submodule']
e.append	64	29	45.31%	['fuzz_diff', 'fuzz_blob', 'fuzz_config', 'fuzz_repo', 'fuzz_submodule']
git.objects.commit.Commit._deserialize	55	28	50.90%	['fuzz_diff', 'fuzz_blob', 'fuzz_config', 'fuzz_repo', 'fuzz_submodule']
stream.close	300	141	47.0%	['fuzz_diff']
git.util.RemoteProgress._parse_progress_line	44	0	0.0%	['fuzz_diff']
repo.git.read_tree	39	17	43.58%	['fuzz_repo', 'fuzz_diff', 'fuzz_config']
buf.find	70	16	22.85%	['fuzz_diff', 'fuzz_blob', 'fuzz_config', 'fuzz_repo', 'fuzz_submodule']
git.objects.submodule.base.Submodule.add	56	30	53.57%	['fuzz_diff', 'fuzz_blob', 'fuzz_config', 'fuzz_repo', 'fuzz_submodule']
git.objects.submodule.base.Submodule.update	94	13	13.82%	['fuzz_diff', 'fuzz_blob', 'fuzz_config', 'fuzz_repo', 'fuzz_submodule']
git.objects.submodule.base.Submodule.move	49	0	0.0%	[]
git.objects.submodule.base.Submodule.remove	60	0	0.0%	[]
s.encode	67	32	47.76%	['fuzz_diff', 'fuzz_blob', 'fuzz_config', 'fuzz_repo', 'fuzz_submodule']
git.repo.base.Repo.blame_incremental	39	0	0.0%	[]
git.repo.base.Repo.blame	75	0	0.0%	[]
git.repo.fun.rev_parse	100	22	22.0%	['fuzz_diff', 'fuzz_blob', 'fuzz_config', 'fuzz_repo', 'fuzz_submodule']
f.readline	56	20	35.71%	['fuzz_diff', 'fuzz_blob', 'fuzz_config', 'fuzz_repo', 'fuzz_submodule']
ref.set_reference	45	10	22.22%	['fuzz_diff', 'fuzz_blob', 'fuzz_config', 'fuzz_repo', 'fuzz_submodule']
git.objects.submodule.root.RootModule.update	104	0	0.0%	[]
git.index.fun.aggressive_tree_merge	36	0	0.0%	[]

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
	[]	[]
git.refs.tag	[]	[]
git.objects.tag	[]	[]
git.cmd	['fuzz_diff', 'fuzz_blob']	[]
git.refs.head	[]	[]
git.refs.remote	[]	[]
git.exc	[]	[]
inspect	[]	[]
...gitpython.fuzzing.fuzz-targets.fuzz_config	['fuzz_config']	[]
git.refs.reference	[]	[]
git.types	[]	[]
subprocess	[]	[]
git.index.fun	[]	[]
os	[]	[]
git.objects.base	['fuzz_diff']	[]
git.objects.commit	[]	[]
configparser	[]	[]
...gitpython.fuzzing.fuzz-targets.fuzz_diff	['fuzz_diff']	[]
git.index.typ	[]	[]
git.objects.submodule.root	[]	[]
...gitpython.fuzzing.fuzz-targets.fuzz_submodule	['fuzz_submodule']	[]
git.objects	[]	[]
git.refs.log	[]	[]
git.index.base	[]	[]
threading	[]	[]
binascii	[]	[]
git.objects.util	['fuzz_diff']	[]
utils	[]	[]
git.objects.fun	['fuzz_repo']	[]
tempfile	[]	[]
importlib	[]	[]
git.remote	['fuzz_blob']	[]
git.index.util	[]	[]
git.refs	[]	[]
git	[]	[]
enum	[]	[]
atheris	[]	[]
stat	[]	[]
uuid	[]	[]
git.objects.tree	['fuzz_repo']	[]
	[]	[]
git.objects.blob	[]	[]
mimetypes	[]	[]
time	[]	[]
functools	[]	[]
textwrap	[]	[]
git.objects.submodule.util	[]	[]
fnmatch	[]	[]
getpass	[]	[]
shlex	[]	[]
warnings	[]	[]
git.compat	['fuzz_repo']	[]
contextlib	[]	[]
typing	[]	[]
gitdb	[]	[]
urllib	[]	[]
calendar	[]	[]
weakref	[]	[]
git.config	['fuzz_blob', 'fuzz_config']	[]
git.repo	[]	[]
git.util	['fuzz_diff', 'fuzz_blob']	[]
locale	[]	[]
git.diff	['fuzz_diff']	[]
shutil	[]	[]
git.objects.submodule	[]	[]
typing_extensions	[]	[]
git.repo.base	['fuzz_blob']	[]
git.repo.fun	['fuzz_blob']	[]
...gitpython.fuzzing.fuzz-targets.fuzz_repo	['fuzz_repo']	[]
re	[]	[]
git.index	[]	[]
git.refs.symbolic	[]	[]
platform	[]	[]
git.db	['fuzz_blob']	[]
pathlib	[]	[]
itertools	[]	[]
io	[]	[]
git.objects.submodule.base	[]	[]
glob	[]	[]
collections	[]	[]
sys	[]	[]
...gitpython.fuzzing.fuzz-targets.fuzz_blob	['fuzz_blob']	[]
datetime	[]	[]
struct	[]	[]
logging	[]	[]
gc	[]	[]

Directories in report

Directory