Project overview: md4c
High level conclusions
Reachability and coverage overview
Warning:
The number of runtime covered functions are larger than the
number of reachable functions. This means that Fuzz Introspector found
there are more functions covered at runtime than what is considered
reachable based on the static analysis. This is a limitation in the
analysis as anything covered at runtime is by definition reachable by the
fuzzers.
This is likely due to a limitation in the static analysis. In this case, the
count of functions covered at runtime is the true value, which means this
is what should be considered "achieved" by the fuzzer.
Use the project functions table below to query all functions that were not covered at runtime.
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: fuzz-mdhtml
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 | 200 | 52.9% |
| gold | [1:9] | 0 | 0.0% |
| yellow | [10:29] | 0 | 0.0% |
| greenyellow | [30:49] | 0 | 0.0% |
| lawngreen | 50+ | 178 | 47.0% |
| All colors | 378 | 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 |
|---|---|---|---|---|
| 50 | 264 | md_pop_openers | call site: 00264 | md_resolve_brackets |
| 29 | 76 | md_analyze_line | call site: 00076 | md_process_line |
| 14 | 249 | md_is_entity | call site: 00249 | md_analyze_emph |
| 14 | 358 | md_process_inlines | call site: 00358 | md_process_table_row |
| 11 | 141 | md_build_attribute | call site: 00141 | md_process_table_block_contents |
| 8 | 329 | md_is_inline_link_spec | call site: 00329 | md_analyze_link_contents |
| 7 | 10 | md_analyze_line | call site: 00010 | md_is_html_block_end_condition |
| 7 | 237 | md_collect_marks | call site: 00237 | md_analyze_marks |
| 6 | 126 | md_build_footnote_def_hashtable | call site: 00126 | md_process_all_blocks |
| 6 | 338 | md_lookup_footnote_def | call site: 00338 | md_process_table_cell |
| 5 | 25 | md_analyze_line | call site: 00025 | md_leave_child_containers |
| 4 | 58 | md_is_link_reference_definition | call site: 00058 | md_push_container_bytes |
Runtime coverage analysis
| Function name | source code lines | source lines hit | percentage hit |
|---|
Files reached
| filename | functions hit |
|---|---|
| build/../test/fuzzers/fuzz-mdhtml.c | 2 |
| src/md4c-html.c | 1 |
| src/md4c.c | 133 |
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
enter_block_callback
|
/src/md4c/src/md4c-html.c | 3 | ['int', 'N/A', 'N/A'] | 6 | 0 | 119 | 22 | 23 | 18 | 0 | 109 | 105 |
Implementing fuzzers that target the above functions will improve reachability such that it becomes:
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 |
|---|
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.
build/../test/fuzzers/fuzz-mdhtml.c
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=['md_pop_openers', 'md_analyze_line', 'md_is_entity', 'md_process_inlines', 'md_build_attribute', 'md_is_inline_link_spec', 'md_collect_marks', 'md_build_footnote_def_hashtable', 'md_lookup_footnote_def']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/md4c/build/../test/fuzzers/fuzz-mdhtml.c | ['fuzz-mdhtml'] | [] |
| /src/md4c/src/md4c.c | ['fuzz-mdhtml'] | ['fuzz-mdhtml'] |
| /src/md4c/src/md4c-html.c | ['fuzz-mdhtml'] | ['fuzz-mdhtml'] |
| /src/md4c/src/entity.c | [] | [] |
Directories in report
| Directory |
|---|
| /src/md4c/build/../test/fuzzers/ |
| /src/md4c/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-mdhtml | fuzzerLogFile-0-jOOAx04Tqj.data | fuzzerLogFile-0-jOOAx04Tqj.data.yaml | fuzz-mdhtml.covreport |