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

Table of contents

Project overview: myanmar-tools
High level conclusions
Reachability and coverage overview
Fuzzers overview
Project functions overview
Fuzzer details
Fuzzer: zawgyi_detector_fuzz_target
Call tree
Fuzz blockers
Runtime coverage analysis
Files reached
Analyses and suggestions
Optimal target analysis
Remaining optimal interesting functions
All functions overview
Fuzz engine guidance
/src/myanmar-tools/clients/cpp/build/../zawgyi_detector_fuzz_target.cpp
Dictionary
Fuzzer function priority
Runtime coverage analysis
Complex functions with low coverage
Files and Directories in report
Files in report
Directories in report
Metadata section
Report generation date: 2024-07-27

Project overview: myanmar-tools

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
24.0%
79 / 334
Cyclomatic complexity statically reachable by fuzzers
20.0%
372 / 1905
Runtime code coverage of functions
4.0%
14 / 334

Fuzzers overview

Fuzzer Fuzzer filename Functions Reached Functions unreached Fuzzer depth Files reached Basic blocks reached Cyclomatic complexity Details
zawgyi_detector_fuzz_target /src/myanmar-tools/clients/cpp/build/../zawgyi_detector_fuzz_target.cpp 197 310 14 12 855 428 zawgyi_detector_fuzz_target.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: zawgyi_detector_fuzz_target

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 140 81.3%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 32 18.6%
All colors 172 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
2 2 1 :

['strlen']

4 18 google_myanmar_tools::ZawgyiUnicodeMarkovModel::Predict(charconst*,int)const call site: 00000 /src/myanmar-tools/clients/cpp/zawgyi_detector.cpp:193
0 0 None 0 369 google_myanmar_tools::ZawgyiUnicodeMarkovModel::ZawgyiUnicodeMarkovModel(unsignedcharconst*) call site: 00000 /src/myanmar-tools/clients/cpp/zawgyi_detector.cpp:172

Runtime coverage analysis

Covered functions
15
Functions that are reachable but not covered
180
Reachable functions
197
Percentage of reachable functions covered
8.63%
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/myanmar-tools/clients/cpp/build/../zawgyi_detector_fuzz_target.cpp 1
/src/myanmar-tools/clients/cpp/zawgyi_detector.cpp 7
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/vlog_is_on.cc 4
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/base/mutex.h 5
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Install/include/glog/logging.h 3
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/logging.cc 7
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Build/glog-Release-prefix/src/glog-Release-build/glog/logging.h 7
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/utilities.cc 8
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/raw_logging.cc 1
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/stacktrace_x86_64-inl.h 2
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/symbolize.cc 23
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/demangle.cc 12

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
google::ParseSpecialName(google::State*) /root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/demangle.cc 1 ['N/A'] 18 0 261 69 30 102 0 315 286
google::(anonymousnamespace)::LogFileObject::Write(bool,long,charconst*,int) /root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/logging.cc 5 ['N/A', 'bool', 'size_t', 'N/A', 'int'] 4 0 933 194 152 58 0 297 265
google::ErrnoLogMessage::~ErrnoLogMessage() /root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/logging.cc 1 ['N/A'] 20 0 51 10 5 259 0 611 245
google::TruncateLogFile(charconst*,long,long) /root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/logging.cc 3 ['N/A', 'size_t', 'size_t'] 14 0 380 68 59 167 1 396 79
google::(anonymousnamespace)::FailureSignalHandler(int,siginfo_t*,void*) /root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/signalhandler.cc 3 ['int', 'N/A', 'N/A'] 9 0 84 15 6 128 0 301 61
GMTGetZawgyiProbability /src/myanmar-tools/clients/cpp/zawgyi_detector.cpp 2 ['N/A', 'N/A'] 4 0 20 3 2 11 0 48 46
google::ParseTemplateArg(google::State*) /root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/demangle.cc 1 ['N/A'] 18 0 73 20 9 101 2 308 44

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

Functions statically reachable by fuzzers
61.0%
203 / 334
Cyclomatic complexity statically reachable by fuzzers
69.0%
1319 / 1905

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

Fuzz engine guidance

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/myanmar-tools/clients/cpp/build/../zawgyi_detector_fuzz_target.cpp

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=['google_myanmar_tools::ZawgyiDetector::ZawgyiDetector()', 'google_myanmar_tools::ZawgyiDetector::ZawgyiDetector()', 'google_myanmar_tools::ZawgyiUnicodeMarkovModel::ZawgyiUnicodeMarkovModel(unsigned char const*)']

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
[] []
/usr/include/pthread.h [] []
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/utilities.cc ['zawgyi_detector_fuzz_target'] []
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/base/googleinit.h [] []
/src/myanmar-tools/clients/cpp/zawgyi_detector.cpp ['zawgyi_detector_fuzz_target'] ['zawgyi_detector_fuzz_target']
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/base/mutex.h ['zawgyi_detector_fuzz_target'] []
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/signalhandler.cc [] []
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/vlog_is_on.cc ['zawgyi_detector_fuzz_target'] []
/usr/include/x86_64-linux-gnu/sys/stat.h [] []
/src/myanmar-tools/clients/cpp/build/../zawgyi_detector_fuzz_target.cpp ['zawgyi_detector_fuzz_target'] []
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/stacktrace_x86_64-inl.h ['zawgyi_detector_fuzz_target'] []
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/raw_logging.cc ['zawgyi_detector_fuzz_target'] []
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/utilities.h [] []
/usr/local/bin/../include/c++/v1/stdexcept [] []
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Build/glog-Release-prefix/src/glog-Release-build/glog/logging.h ['zawgyi_detector_fuzz_target'] []
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Install/include/glog/logging.h ['zawgyi_detector_fuzz_target'] []
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/logging.cc ['zawgyi_detector_fuzz_target'] []
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/symbolize.cc ['zawgyi_detector_fuzz_target'] []
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/demangle.cc ['zawgyi_detector_fuzz_target'] []

Directories in report

Directory
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Source/src/base/
/src/myanmar-tools/clients/cpp/
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Build/glog/Build/glog-Release-prefix/src/glog-Release-build/glog/
/usr/include/
/root/.hunter/_Base/5ead1e0/d112797/ead1bc1/Install/include/glog/
/src/myanmar-tools/clients/cpp/build/../
/usr/include/x86_64-linux-gnu/sys/
/usr/local/bin/../include/c++/v1/

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
zawgyi_detector_fuzz_target fuzzerLogFile-0-UgHzmukKFC.data fuzzerLogFile-0-UgHzmukKFC.data.yaml zawgyi_detector_fuzz_target.covreport