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

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 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 details

Fuzzer: libpng_read_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 392 57.1%
gold [1:9] 12 1.74%
yellow [10:29] 11 1.60%
greenyellow [30:49] 11 1.60%
lawngreen 50+ 260 37.9%
All colors 686 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
88 494 LLVMFuzzerTestOneInput call site: 00494 png_image_read_colormap
37 298 OSS_FUZZ_png_gamma_16bit_correct call site: 00298 png_build_16bit_table
31 237 OSS_FUZZ_png_init_read_transformations call site: 00237 OSS_FUZZ_png_set_rgb_coefficients
25 646 png_image_read_direct call site: 00646 png_image_read_background
11 608 png_image_skip_unused_chunks call site: 00608 png_image_read_and_map
10 588 OSS_FUZZ_png_set_alpha_mode_fixed call site: 00588 png_image_read_colormapped
9 147 png_crc_finish_critical call site: 00147 png_cache_unknown_chunk
8 165 OSS_FUZZ_png_chunk_report call site: 00165 OSS_FUZZ_png_chunk_report
8 415 OSS_FUZZ_png_do_read_transformations call site: 00415 png_do_quantize
6 270 OSS_FUZZ_png_init_read_transformations call site: 00270 OSS_FUZZ_png_gamma_significant
6 355 LLVMFuzzerTestOneInput call site: 00355 OSS_FUZZ_png_read_start_row
5 10 OSS_FUZZ_png_create_png_struct call site: 00010 OSS_FUZZ_png_warning

Runtime coverage analysis

Covered functions
212
Functions that are reachable but not covered
63
Reachable functions
196
Percentage of reachable functions covered
67.86%
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
/src/libpng/contrib/oss-fuzz/libpng_read_fuzzer.cc 3
/src/libpng/png.c 33
/src/libpng/pngread.c 32
/src/libpng/pngmem.c 10
/src/libpng/pngerror.c 20
/src/libpng/pngrio.c 2
/src/libpng/pngrtran.c 38
/src/libpng/pngrutil.c 23
/src/libpng/pngset.c 5
/src/libpng/pngget.c 3
/src/libpng/pngtrans.c 13

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
png_handle_iCCP /src/libpng/pngrutil.c 3 ['N/A', 'N/A', 'int'] 9 0 533 79 28 41 0 261 93
png_handle_iTXt /src/libpng/pngrutil.c 3 ['N/A', 'N/A', 'int'] 8 0 468 80 28 36 0 237 86
OSS_FUZZ_png_set_sCAL /src/libpng/pngset.c 5 ['N/A', 'N/A', 'int', 'double', 'double'] 5 0 60 9 4 17 0 122 79
OSS_FUZZ_png_set_quantize /src/libpng/pngrtran.c 6 ['N/A', 'N/A', 'int', 'int', 'N/A', 'int'] 6 0 1572 190 58 14 0 113 58
OSS_FUZZ_png_read_png /src/libpng/pngread.c 4 ['N/A', 'N/A', 'int', 'N/A'] 11 0 379 67 22 132 0 1317 46
png_handle_pCAL /src/libpng/pngrutil.c 3 ['N/A', 'N/A', 'int'] 8 0 485 64 23 27 0 159 43
OSS_FUZZ_png_check_keyword /src/libpng/pngset.c 3 ['N/A', 'N/A', 'N/A'] 3 0 237 46 17 7 0 65 39
OSS_FUZZ_png_set_cHRM_XYZ /src/libpng/pngset.c 11 ['N/A', 'N/A', 'double', 'double', 'double', 'double', 'double', 'double', 'double', 'double', 'double'] 6 0 63 3 2 14 0 70 39

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

Functions statically reachable by fuzzers
56.0%
225 / 401
Cyclomatic complexity statically reachable by fuzzers
72.0%
2312 / 3194

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

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
[] []
/src/libpng/pngget.c ['libpng_read_fuzzer'] ['libpng_read_fuzzer']
/src/libpng/pngrio.c ['libpng_read_fuzzer'] ['libpng_read_fuzzer']
/src/libpng/pngerror.c ['libpng_read_fuzzer'] ['libpng_read_fuzzer']
/src/libpng/pngmem.c ['libpng_read_fuzzer'] ['libpng_read_fuzzer']
/src/libpng/pngread.c ['libpng_read_fuzzer'] ['libpng_read_fuzzer']
/src/libpng/pngrtran.c ['libpng_read_fuzzer'] ['libpng_read_fuzzer']
/usr/local/bin/../include/c++/v1/stdexcept [] []
/src/libpng/png.c ['libpng_read_fuzzer'] ['libpng_read_fuzzer']
/src/libpng/pngtrans.c ['libpng_read_fuzzer'] ['libpng_read_fuzzer']
/src/libpng/pngset.c ['libpng_read_fuzzer'] ['libpng_read_fuzzer']
/src/libpng/contrib/oss-fuzz/libpng_read_fuzzer.cc ['libpng_read_fuzzer'] ['libpng_read_fuzzer']
/src/libpng/pngrutil.c ['libpng_read_fuzzer'] ['libpng_read_fuzzer']

Directories in report

Directory
/usr/local/bin/../include/c++/v1/
/src/libpng/contrib/oss-fuzz/
/src/libpng/