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

Table of contents

Project overview: cmake
High level conclusions
Reachability and coverage overview
Fuzzers overview
Project functions overview
Fuzzer details
Fuzzer: xml_parser_fuzzer
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

Project overview: cmake

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
15.2%
57/375
Cyclomatic complexity statically reachable by fuzzers
11.48%
371/3231
Functions covered at runtime
192

Fuzzers overview

Fuzzer Fuzzer filename Functions Reached Functions unreached Fuzzer depth Files reached Basic blocks reached Cyclomatic complexity Details
xml_parser_fuzzer Tests/Fuzzing/xml_parser_fuzzer.cc 57 318 9 4 764 371 xml_parser_fuzzer.cc

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

Call tree

The following is the call tree with color coding for which functions are hit/not hit. This info is based on the coverage achieved of all fuzzers together and not just this specific fuzzer. We use the following coloring scheme where min/max is an interval [min:max) (max non-inclusive) to color the callsite based on how many times the callsite is covered at run time.
Min Max Color
0 1 red
1 10 gold
10 30 yellow
30 50 greenyellow
50 1000000000000 lawngreen

For further technical details on the call tree overview, please see the Glossary .

The distribution of callsites in terms of coloring is
Color Callsite count Percentage
red 25 30.1%
gold 0 0.0%
yellow 0 0.0%
greenyellow 0 0.0%
lawngreen 58 69.8%
All colors 83 100

Full call tree

The following link provides a visualisation of the full call tree overlaid with coverage information: full call tree

For further technical details on how the call tree is generated, please see the Glossary .

Fuzz blockers

The followings nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked Calltree index Parent function Callsite Largest blocked function
15 16 getDebugLevel call site setContext
4 51 poolCopyString call site addBinding
3 47 lookup call site lookup
1 33 poolGrow call site lookup
1 58 XML_Parse call site startParsing
1 81 cmXMLParser::~cmXMLParser() call site __cxa_begin_catch

Branch Blockers [Click to view]

Runtime coverage analysis

Covered functions
192
Functions that are reachable but not covered
20
Reachable functions
57
Percentage of reachable functions covered
64.91%
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
Tests/Fuzzing/xml_parser_fuzzer.cc 1
Source/cmXMLParser.cxx 6
Utilities/cmexpat/lib/xmlparse.c 32
Utilities/cmexpat/lib/siphash.h 4

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
XML_ExternalEntityParserCreate /src/CMake/Utilities/cmexpat/lib/xmlparse.c 3 ['struct.XML_ParserStruct *', 'char *', 'char *'] 29 0 248 22 9 153 0 1647 1439
normal_contentTok /src/CMake/Utilities/cmexpat/lib/xmltok_impl.c 4 ['struct.encoding *', 'char *', 'char *', 'char **'] 5 0 434 88 25 10 0 220 220
big2_contentTok /src/CMake/Utilities/cmexpat/lib/xmltok_impl.c 4 ['struct.encoding *', 'char *', 'char *', 'char **'] 6 0 464 93 27 11 0 184 167
little2_contentTok /src/CMake/Utilities/cmexpat/lib/xmltok_impl.c 4 ['struct.encoding *', 'char *', 'char *', 'char **'] 6 0 460 93 27 11 0 184 126
normal_prologTok /src/CMake/Utilities/cmexpat/lib/xmltok_impl.c 4 ['struct.encoding *', 'char *', 'char *', 'char **'] 2 0 809 165 34 7 0 155 89
big2_prologTok /src/CMake/Utilities/cmexpat/lib/xmltok_impl.c 4 ['struct.encoding *', 'char *', 'char *', 'char **'] 3 0 807 162 30 8 0 124 66

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

Functions statically reachable by fuzzers
61.07%
229/375
Cyclomatic complexity statically reachable by fuzzers
76.69%
2478 / 3231

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
XML_Parse 152 38 25.0% ['xml_parser_fuzzer']
XML_ParseBuffer 63 32 50.79% ['xml_parser_fuzzer']
XML_GetBuffer 121 47 38.84% ['xml_parser_fuzzer']
XML_ErrorString 103 49 47.57% []
parserCreate 111 53 47.74% []
handleUnknownEncoding 32 4 12.5% []
doProlog 1027 397 38.65% []
processXmlDecl 89 47 52.80% []
storeAtts 465 110 23.65% []
getAttributeId 58 20 34.48% []
appendAttributeValue 196 105 53.57% []
storeEntityValue 182 63 34.61% []
generate_hash_secret_salt 41 6 14.63% ['xml_parser_fuzzer']
initScan 109 40 36.69% []
little2_prologTok 241 40 16.59% []
little2_updatePosition 31 10 32.25% []
big2_prologTok 241 40 16.59% []
big2_updatePosition 31 10 32.25% []

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/CMake/Utilities/cmexpat/lib/xmlrole.c [] []
/src/CMake/Utilities/cmexpat/lib/xmltok.c [] []
/src/CMake/Tests/Fuzzing/xml_parser_fuzzer.cc ['xml_parser_fuzzer'] ['xml_parser_fuzzer']
/src/CMake/Utilities/cmexpat/lib/siphash.h ['xml_parser_fuzzer'] ['xml_parser_fuzzer']
/src/CMake/Utilities/cmexpat/lib/xmltok_ns.c [] []
/src/CMake/Source/cmXMLParser.cxx ['xml_parser_fuzzer'] ['xml_parser_fuzzer']
/src/CMake/Utilities/cmexpat/lib/xmltok_impl.c [] []
/src/CMake/Utilities/cmexpat/lib/xmlparse.c ['xml_parser_fuzzer'] ['xml_parser_fuzzer']
/usr/include/ctype.h [] []

Directories in report

Directory
/src/CMake/Utilities/cmexpat/lib/
/usr/include/
/src/CMake/Source/
/src/CMake/Tests/Fuzzing/