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

Table of contents

Project overview: onednn
High level conclusions
Reachability and coverage overview
Fuzzers overview
Project functions overview
Fuzzer details
Fuzzer: fuzz_json
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-09-25

Project overview: onednn

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
85.0%
11 / 13
Cyclomatic complexity statically reachable by fuzzers
96.0%
89 / 93
Runtime code coverage of functions
69.0%
9 / 13

Fuzzers overview

Fuzzer Fuzzer filename Functions Reached Functions unreached Fuzzer depth Files reached Basic blocks reached Cyclomatic complexity Details
fuzz_json /src/fuzz_json.cpp 29 21 4 2 146 113 fuzz_json.cpp

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_json

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 0 0.0%
gold [1:9] 2 8.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 23 92.0%
All colors 25 100

Fuzz blockers

The followings are the branches where fuzzer fails to bypass.

Unique non-covered Complexity Unique Reachable Complexities Unique Reachable Functions All non-covered Complexity All Reachable Complexity Function Name Function Callsite Blocked Branch
0 0 6 :

['std::__1::__map_iterator , std::__1::allocator >, dnnl::impl::graph::utils::json::read_helper_t::entry_t>, std::__1::__tree_node , std::__1::allocator >, dnnl::impl::graph::utils::json::read_helper_t::entry_t>, void*>*, long> >::operator++()', 'std::__1::map , std::__1::allocator >, dnnl::impl::graph::utils::json::read_helper_t::entry_t, std::__1::less , std::__1::allocator > >, std::__1::allocator , std::__1::allocator > const, dnnl::impl::graph::utils::json::read_helper_t::entry_t> > >::end()', 'std::__1::__map_iterator , std::__1::allocator >, dnnl::impl::graph::utils::json::read_helper_t::entry_t>, std::__1::__tree_node , std::__1::allocator >, dnnl::impl::graph::utils::json::read_helper_t::entry_t>, void*>*, long> >::operator->() const', 'std::__1::operator!=(std::__1::__map_iterator , std::__1::allocator >, dnnl::impl::graph::utils::json::read_helper_t::entry_t>, std::__1::__tree_node , std::__1::allocator >, dnnl::impl::graph::utils::json::read_helper_t::entry_t>, void*>*, long> > const&, std::__1::__map_iterator , std::__1::allocator >, dnnl::impl::graph::utils::json::read_helper_t::entry_t>, std::__1::__tree_node , std::__1::allocator >, dnnl::impl::graph::utils::json::read_helper_t::entry_t>, void*>*, long> > const&)', 'std::__1::map , std::__1::allocator >, dnnl::impl::graph::utils::json::read_helper_t::entry_t, std::__1::less , std::__1::allocator > >, std::__1::allocator , std::__1::allocator > const, dnnl::impl::graph::utils::json::read_helper_t::entry_t> > >::begin()', 'std::__1::map , std::__1::allocator >, int, std::__1::less , std::__1::allocator > >, std::__1::allocator , std::__1::allocator > const, int> > >::count(std::__1::basic_string , std::__1::allocator > const&) const']

0 0 dnnl::impl::graph::utils::json::read_helper_t::read_fields(dnnl::impl::graph::utils::json::json_reader_t*) call site: 00000 /src/oneDNN/src/graph/utils/json.hpp:570

Runtime coverage analysis

Covered functions
10
Functions that are reachable but not covered
10
Reachable functions
29
Percentage of reachable functions covered
65.52%
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
/src/fuzz_json.cpp 1
/src/oneDNN/src/graph/utils/json.hpp 11

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

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

Functions statically reachable by fuzzers
85.0%
11 / 13
Cyclomatic complexity statically reachable by fuzzers
96.0%
89 / 93

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

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/oneDNN/src/graph/utils/json.hpp ['fuzz_json'] ['fuzz_json']
/usr/local/bin/../include/c++/v1/stdexcept [] []
/src/fuzz_json.cpp ['fuzz_json'] ['fuzz_json']

Directories in report

Directory
/usr/local/bin/../include/c++/v1/
/src/oneDNN/src/graph/utils/
/src/

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_json fuzzerLogFile-0-ZuSQiL60uS.data fuzzerLogFile-0-ZuSQiL60uS.data.yaml fuzz_json.covreport