Fuzz introspector
For issues and ideas: https://github.com/ossf/fuzz-introspector/issues
Project coverage

Table of contents

Project overview: gitdb
High level conclusions
Reachability and coverage overview
Fuzzers overview
Project functions overview
Fuzzer details
Fuzzer: fuzz_gitdb
Call tree
Fuzz blockers
Runtime coverage analysis
Files reached
Analyses and suggestions
Optimal target analysis
Remaining optimal interesting functions
All functions overview
Runtime coverage analysis
Complex functions with low coverage
Files and Directories in report
Files in report
Directories in report
Metadata section
Function call coverage
Function in each files in report
Report generation date: 2023-06-07

Project overview: gitdb

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
19.0%
50 / 262
Cyclomatic complexity statically reachable by fuzzers
19.0%
165 / 854
Runtime code coverage of functions
1.0%
3 / 262

Fuzzers overview

Fuzzer Fuzzer filename Functions Reached Functions unreached Fuzzer depth Files reached Basic blocks reached Cyclomatic complexity Details
fuzz_gitdb /src/fuzz_gitdb.py 115 349 7 11 45 357 fuzz_gitdb.py

Project functions overview

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 details

Fuzzer: fuzz_gitdb

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

Full calltree

Call tree overview bitmap:

The distribution of callsites in terms of coloring is
Color Runtime hitcount Callsite count Percentage
red 0 157 76.5%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 48 23.4%
All colors 205 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
61 65 gitdb.db.mem.MemoryDB.stream_copy call site: 00065 gitdb.fun.write_object
15 7 ...fuzz_gitdb.fuzz_decompression_map_reader call site: 00007 gitdb.stream.DecompressMemMapReader.read
14 137 ...fuzz_gitdb.fuzz_loose_obj_db call site: 00137 gitdb.db.loose.LooseObjectDB._map_loose_object
11 31 ...fuzz_gitdb.fuzz_loose_obj_db call site: 00031 gitdb.db.loose.LooseObjectDB.sha_iter
10 47 gitdb.db.mem.MemoryDB.stream_copy call site: 00047 gitdb.db.loose.LooseObjectDB.readable_db_object_path
8 196 gitdb.base.OPackInfo.__init__ call site: 00196 gitdb.fun.stream_copy
7 152 gitdb.util._RandomAccessBytesIO.__init__ call site: 00152 gitdb.util.file_contents_ro_filepath
5 169 gitdb.stream.DecompressMemMapReader._parse_header_info call site: 00169 gitdb.base.OStream.__init__
4 131 gitdb.util._retry call site: 00131 os.remove
4 163 ...fuzz_gitdb.fuzz_loose_obj_db call site: 00163 gitdb.db.loose.LooseObjectDB._map_loose_object
4 182 ...fuzz_gitdb.fuzz_pack_file call site: 00182 gitdb.pack.PackFile.stream_iter
3 188 gitdb.pack.pack_object_at call site: 00188 gitdb.util.byte_ord

Runtime coverage analysis

Covered functions
9
Functions that are reachable but not covered
112
Reachable functions
115
Percentage of reachable functions covered
2.61%
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_gitdb 25
gitdb.stream 23
gitdb.db.loose 41
gitdb.db.mem 10
gitdb.db.base 2
gitdb.utils.encoding 2
gitdb.base 2
gitdb.fun 17
gitdb.pack 12
gitdb.util 14

Analyses and suggestions

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
gitdb.pack.PackEntity.is_valid_stream gitdb.pack 3 ['N/A', 'N/A', 'N/A'] 4 0 2 2 4 54 0 175 73
gitdb.stream.DeltaApplyReader._set_cache_too_slow_without_c gitdb.stream 2 ['N/A', 'N/A'] 4 0 3 2 4 38 1 125 64
gitdb.fun.connect_deltas gitdb.fun 1 ['N/A'] 2 0 4 13 8 19 0 72 53
gitdb.pack.PackEntity.write_pack gitdb.pack 6 ['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A'] 4 0 5 8 6 34 1 110 50

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

Functions statically reachable by fuzzers
32.0%
85 / 262
Cyclomatic complexity statically reachable by fuzzers
35.0%
296 / 854

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

Runtime coverage analysis

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
f.write 44 10 22.72% ['fuzz_gitdb']
m.close 51 19 37.25% ['fuzz_gitdb']
l.strip 172 64 37.20% []
stream.delta_info.tobytes 299 159 53.17% []

Files and Directories in report

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
[] []
zlib [] []
gitdb.stream ['fuzz_gitdb'] []
gitdb.db.base ['fuzz_gitdb'] []
sha [] []
codecs [] []
gitdb.base ['fuzz_gitdb'] []
struct [] []
gitdb.db.git [] []
binascii [] []
[] []
io [] []
gitdb.db.loose ['fuzz_gitdb'] []
gitdb.utils.encoding ['fuzz_gitdb'] []
gitdb [] []
gitdb.pack ['fuzz_gitdb'] []
gitdb.fun ['fuzz_gitdb'] []
time [] []
gitdb.db [] []
...fuzz_gitdb ['fuzz_gitdb'] []
os [] []
gitdb.const [] []
gitdb.db.ref [] []
itertools [] []
gitdb.exc [] []
hashlib [] []
gitdb.typ [] []
gitdb.utils [] []
functools [] []
smmap [] []
sys [] []
atheris [] []
gitdb.db.mem ['fuzz_gitdb'] []
gitdb_speedups [] []
tempfile [] []
gitdb.db.pack [] []
array [] []
mmap [] []
gitdb.util ['fuzz_gitdb'] []
glob [] []

Directories in report

Directory

Metadata section

This sections shows the raw data that is used to produce this report. This is mainly used for further processing and developer debugging.

Fuzzer Calltree file Program data file Coverage file
fuzz_gitdb fuzzerLogFile-fuzz_gitdb.data fuzzerLogFile-fuzz_gitdb.data.yaml all_cov.json