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

Fuzzer details

Fuzzer: pcre2_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 35 12.0%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 256 87.9%
All colors 291 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
12 2506 5 :

['_pcre2_is_newline_8', '_pcre2_was_newline_8', 'match', '_pcre2_valid_utf_8', 'memchr']

12 2506 pcre2_match_8 call site: 00195 /src/pcre2/src/pcre2_match.c:6790
2 2 1 :

['_pcre2_strlen_8']

14 2508 pcre2_match_8 call site: 00193 /src/pcre2/src/pcre2_match.c:6492
2 2 1 :

['_pcre2_strlen_8']

14 1623 pcre2_dfa_match_8 call site: 00243 /src/pcre2/src/pcre2_dfa_match.c:3363
2 2 1 :

['_pcre2_strlen_8']

2 2426 pcre2_compile_8 call site: 00004 /src/pcre2/src/pcre2_compile.c:10198
0 1376 12 :

['get_ucp', 'read_repeat_counts', '_pcre2_check_escape_8', '_pcre2_strncmp_c8_8', 'read_number', 'handle_escdsw', 'manage_callouts', 'check_posix_name', 'read_name', 'check_posix_syntax', '_pcre2_is_newline_8', '_pcre2_strncmp_8']

0 1376 parse_regex call site: 00022 /src/pcre2/src/pcre2_compile.c:3200
0 1376 12 :

['read_repeat_counts', 'get_ucp', '_pcre2_check_escape_8', 'read_number', '_pcre2_strncmp_c8_8', 'handle_escdsw', 'manage_callouts', 'check_posix_name', 'read_name', 'check_posix_syntax', '_pcre2_is_newline_8', '_pcre2_strncmp_8']

0 1376 parse_regex call site: 00045 /src/pcre2/src/pcre2_compile.c:3766
0 6 1 :

['pcre2_code_free_8']

0 6 pcre2_compile_8 call site: 00147 /src/pcre2/src/pcre2_compile.c:10906
0 0 None 12 2506 pcre2_match_8 call site: 00194 /src/pcre2/src/pcre2_match.c:6567
0 0 None 12 2506 pcre2_match_8 call site: 00194 /src/pcre2/src/pcre2_match.c:6717
0 0 None 12 2476 pcre2_match_8 call site: 00195 /src/pcre2/src/pcre2_match.c:6822
0 0 None 12 2476 pcre2_match_8 call site: 00195 /src/pcre2/src/pcre2_match.c:6942
0 0 None 12 2476 pcre2_match_8 call site: 00205 /src/pcre2/src/pcre2_match.c:7374

Runtime coverage analysis

Covered functions
82
Functions that are reachable but not covered
9
Reachable functions
86
Percentage of reachable functions covered
89.53%
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
pcre2_fuzzsupport.c 2
pcre2_compile.c 32
pcre2_string_utils.c 5
pcre2_valid_utf.c 1
pcre2_newline.c 2
pcre2_ord2utf.c 1
pcre2_chkdint.c 1
pcre2_find_bracket.c 1
pcre2_auto_possess.c 5
pcre2_xclass.c 1
pcre2_study.c 6
pcre2_match_data.c 2
pcre2_context.c 8
pcre2_match.c 4
pcre2_extuni.c 1
pcre2_script_run.c 1
pcre2_dfa_match.c 4
pcre2_error.c 1

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/pcre2/src/pcre2_match.c ['pcre2_fuzzer'] ['pcre2_fuzzer']
/src/pcre2/src/pcre2_context.c ['pcre2_fuzzer'] ['pcre2_fuzzer']
/src/pcre2/src/pcre2_compile.c ['pcre2_fuzzer'] ['pcre2_fuzzer']
/src/pcre2/src/pcre2_extuni.c ['pcre2_fuzzer'] ['pcre2_fuzzer']
/src/pcre2/src/pcre2_error.c ['pcre2_fuzzer'] ['pcre2_fuzzer']
/src/pcre2/src/pcre2_fuzzsupport.c ['pcre2_fuzzer'] ['pcre2_fuzzer']
/src/pcre2/src/pcre2_study.c ['pcre2_fuzzer'] ['pcre2_fuzzer']
/src/pcre2/src/pcre2_valid_utf.c ['pcre2_fuzzer'] ['pcre2_fuzzer']
/src/pcre2/src/pcre2_script_run.c ['pcre2_fuzzer'] ['pcre2_fuzzer']
/src/pcre2/src/pcre2_ord2utf.c ['pcre2_fuzzer'] ['pcre2_fuzzer']
/src/pcre2/src/pcre2_xclass.c ['pcre2_fuzzer'] ['pcre2_fuzzer']
/src/pcre2/src/pcre2_dfa_match.c ['pcre2_fuzzer'] ['pcre2_fuzzer']
/src/pcre2/src/pcre2_chkdint.c ['pcre2_fuzzer'] ['pcre2_fuzzer']
/src/pcre2/src/pcre2_string_utils.c ['pcre2_fuzzer'] ['pcre2_fuzzer']
/src/pcre2/src/pcre2_auto_possess.c ['pcre2_fuzzer'] ['pcre2_fuzzer']
/src/pcre2/src/pcre2_newline.c ['pcre2_fuzzer'] ['pcre2_fuzzer']
/src/pcre2/src/pcre2_find_bracket.c ['pcre2_fuzzer'] ['pcre2_fuzzer']
/src/pcre2/src/pcre2_match_data.c ['pcre2_fuzzer'] ['pcre2_fuzzer']

Directories in report

Directory
/src/pcre2/src/