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

Table of contents

Project overview: bs4
High level conclusions
Reachability and coverage overview
Fuzzers overview
Project functions overview
Fuzzer details
Fuzzer: bs4_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
Metadata section
Function call coverage
Function in each files in report
Report generation date: 2023-06-07

Project overview: bs4

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
8.0%
36 / 457
Cyclomatic complexity statically reachable by fuzzers
10.0%
168 / 1679
Runtime code coverage of functions
62.0%
283 / 457

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.

Fuzzers overview

Fuzzer Fuzzer filename Functions Reached Functions unreached Fuzzer depth Files reached Basic blocks reached Cyclomatic complexity Details
bs4_fuzzer /src/bs4_fuzzer.py 286 757 6 7 166 921 bs4_fuzzer.py

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

Full calltree

Call tree overview bitmap:

The distribution of callsites in terms of coloring is
Color Runtime hitcount Callsite count Percentage
red 0 270 64.2%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 150 35.7%
All colors 420 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
66 284 bs4.element.SoupStrainer.search_tag call site: 00284 bs4.element.SoupStrainer._matches
65 216 bs4.element.SoupStrainer._matches call site: 00216 html5lib.treebuilders._base.Node.next_sibling.prefix.string.search
48 95 bs4.element.SoupStrainer._normalize_search_value call site: 00095 bs4.BeautifulSoup.decode
28 144 bs4.BeautifulSoup.decode call site: 00144 bs4.element.SoupStrainer._normalize_search_value
9 29 bs4.builder.TreeBuilderRegistry.lookup call site: 00029 candidate_set.intersection
5 4 ...bs4_fuzzer.TestOneInput call site: 00004 warnings.warn
5 182 bs4.element.ResultSet.__init__ call site: 00182 bs4.element.ResultSet.__init__
5 209 bs4.element.SoupStrainer._matches call site: 00209 bs4.element.SoupStrainer._matches
4 415 bs4.element.Tag.prettify call site: 00415 bs4.element.Tag.decode
3 198 bs4.element.SoupStrainer.search_tag call site: 00198 bs4.element.SoupStrainer._matches
2 10 bs4.BeautifulSoup.__init__ call site: 00010 warnings.warn
2 42 bs4.BeautifulSoup.__init__ call site: 00042 .isinstance

Runtime coverage analysis

Covered functions
308
Functions that are reachable but not covered
248
Reachable functions
286
Percentage of reachable functions covered
13.29%
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
/ 1
...bs4_fuzzer 8
bs4 38
bs4.builder 7
bs4.element 243
bs4.formatter 6
bs4.dammit 1

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
bs4.element.Tag.select bs4.element 5 ['N/A', 'N/A', 'N/A', 'N/A', 'N/A'] 9 0 1 3 4 190 1 712 685
bs4.dammit.EncodingDetector.encodings bs4.dammit 1 ['N/A'] 1 0 7 8 6 18 0 63 51
bs4.dammit.UnicodeDammit.__init__ bs4.dammit 8 ['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A'] 2 0 2 6 5 17 1 59 41
bs4.element.PageElement.insert bs4.element 3 ['N/A', 'N/A', 'N/A'] 2 0 4 14 9 11 13 51 39

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

Functions statically reachable by fuzzers
35.0%
162 / 457
Cyclomatic complexity statically reachable by fuzzers
42.0%
705 / 1679

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
bs4.element.SoupStrainer._matches 41 19 46.34% ['bs4_fuzzer']
soupsieve.css_parser.CSSParser.parse_pseudo_class 66 30 45.45% []
soupsieve.css_match.Inputs.parse_value 49 2 4.081% []
soupsieve.css_match.CSSMatch.extended_language_filter 33 0 0.0% []
soupsieve.css_match.CSSMatch.match_nth 80 3 3.75% []
soupsieve.css_match.CSSMatch.match_indeterminate.get_parent_form 46 0 0.0% []
soupsieve.css_match.CSSMatch.match_lang 61 0 0.0% []
soupsieve.css_match.CSSMatch.match_dir 43 0 0.0% []
x.lower 501 257 51.29% []
bs4.builder._html5lib.TreeBuilderForHtml5lib.testSerializer.serializeElement 34 0 0.0% []
bs4.builder._htmlparser.parse_starttag 43 0 0.0% []
html.entities.codepoint2name.items 1016 72 7.086% []

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
[] []
bs4.dammit ['bs4_fuzzer'] []
bs4.builder._html5lib [] []
sys [] []
traceback [] []
bs4.builder._htmlparser [] []
bs4.diagnose [] []
time [] []
warnings [] []
atheris [] []
bs4.formatter ['bs4_fuzzer'] []
bs4.builder._lxml [] []
typing [] []
pstats [] []
unicodedata [] []
soupsieve.__meta__ [] []
bs4 ['bs4_fuzzer'] []
soupsieve.pretty [] []
collections [] []
bs4.element ['bs4_fuzzer'] []
charset_normalizer [] []
codecs [] []
lxml [] []
soupsieve.css_match [] []
re [] []
soupsieve.css_types [] []
[] []
functools [] []
chardet [] []
copyreg [] []
html [] []
tempfile [] []
html5lib [] []
cchardet [] []
os [] []
io [] []
soupsieve.util [] []
soupsieve [] []
random [] []
logging [] []
soupsieve.css_parser [] []
datetime [] []
...bs4_fuzzer ['bs4_fuzzer'] []
cProfile [] []
bs4.builder ['bs4_fuzzer'] []

Directories in report

Directory

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
bs4_fuzzer fuzzerLogFile-bs4_fuzzer.data fuzzerLogFile-bs4_fuzzer.data.yaml all_cov.json