High level conclusions

Fuzzers reach 56.91% code coverage.

Reachability and coverage overview

Functions statically reachable by fuzzers

135 / 557

Cyclomatic complexity statically reachable by fuzzers

569 / 1974

Runtime code coverage of functions

317 / 557

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.

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

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	332	45.9%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	391	54.0%
All colors	723	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
63	525	soupsieve.css_match.CSSMatch.match_selectors	call site: 00525	soupsieve.css_match.Inputs.parse_value
31	677	soupsieve.css_match.CSSMatch.match_selectors	call site: 00677	soupsieve.css_match.CSSMatch.match_dir
20	208	soupsieve.css_parser.CSSParser.parse_pseudo_class	call site: 00208	soupsieve.css_parser.CSSParser.parse_selectors
18	601	soupsieve.css_match.CSSMatch.match_lang	call site: 00601	soupsieve.css_match._DocumentNav.iter_attributes
15	661	soupsieve.css_match.CSSMatch.match_selectors	call site: 00661	soupsieve.css_match.CSSMatch.match_indeterminate.get_parent_form
13	12	bs4.BeautifulSoup.__init__	call site: 00012	bs4.builder.TreeBuilderRegistry.lookup
11	145	soupsieve.css_parser.CSSParser.parse_selectors	call site: 00145	.print
8	48	bs4.BeautifulSoup.__init__	call site: 00048	bs4.BeautifulSoup._decode_markup
8	652	soupsieve.css_match.CSSMatch.match_selectors	call site: 00652	soupsieve.css_match._DocumentNav.get_tag_descendants
7	200	soupsieve.css_parser.CSSParser.parse_pseudo_class	call site: 00200	soupsieve.css_types.SelectorList.__init__
6	30	bs4.builder.TreeBuilderRegistry.lookup	call site: 00030	.len
6	40	bs4.BeautifulSoup.__init__	call site: 00040	warnings.warn

Runtime coverage analysis

Covered functions

337

Functions that are reachable but not covered

140

Reachable functions

242

Percentage of reachable functions covered

42.15%

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
...fuzz_match	8
bs4	37
bs4.builder	7
bs4.element	4
soupsieve	8
soupsieve.css_parser	80
soupsieve.util	3
soupsieve.css_match	111
soupsieve.css_types	2

Fuzzer: fuzz_closest

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	326	45.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	395	54.7%
All colors	721	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
63	521	soupsieve.css_match.CSSMatch.match_selectors	call site: 00521	soupsieve.css_match.Inputs.parse_value
31	673	soupsieve.css_match.CSSMatch.match_selectors	call site: 00673	soupsieve.css_match.CSSMatch.match_dir
20	204	soupsieve.css_parser.CSSParser.parse_pseudo_class	call site: 00204	soupsieve.css_parser.CSSParser.parse_selectors
18	597	soupsieve.css_match.CSSMatch.match_lang	call site: 00597	soupsieve.css_match._DocumentNav.iter_attributes
15	657	soupsieve.css_match.CSSMatch.match_selectors	call site: 00657	soupsieve.css_match.CSSMatch.match_indeterminate.get_parent_form
13	8	bs4.BeautifulSoup.__init__	call site: 00008	bs4.builder.TreeBuilderRegistry.lookup
11	141	soupsieve.css_parser.CSSParser.parse_selectors	call site: 00141	.print
8	44	bs4.BeautifulSoup.__init__	call site: 00044	bs4.BeautifulSoup._decode_markup
8	648	soupsieve.css_match.CSSMatch.match_selectors	call site: 00648	soupsieve.css_match._DocumentNav.get_tag_descendants
7	196	soupsieve.css_parser.CSSParser.parse_pseudo_class	call site: 00196	soupsieve.css_types.SelectorList.__init__
6	26	bs4.builder.TreeBuilderRegistry.lookup	call site: 00026	.len
6	36	bs4.BeautifulSoup.__init__	call site: 00036	warnings.warn

Runtime coverage analysis

Covered functions

337

Functions that are reachable but not covered

137

Reachable functions

242

Percentage of reachable functions covered

43.39%

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
...fuzz_closest	7
bs4	37
bs4.builder	7
bs4.element	4
soupsieve	8
soupsieve.css_parser	80
soupsieve.util	3
soupsieve.css_match	112
soupsieve.css_types	2

Fuzzer: fuzz_filter

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	352	47.6%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	386	52.3%
All colors	738	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
63	543	soupsieve.css_match.CSSMatch.match_selectors	call site: 00543	soupsieve.css_match.Inputs.parse_value
30	696	soupsieve.css_match.CSSMatch.match_selectors	call site: 00696	soupsieve.css_match.CSSMatch.match_dir
20	204	soupsieve.css_parser.CSSParser.parse_pseudo_class	call site: 00204	soupsieve.css_parser.CSSParser.parse_selectors
18	619	soupsieve.css_match.CSSMatch.match_lang	call site: 00619	soupsieve.css_match._DocumentNav.iter_attributes
15	680	soupsieve.css_match.CSSMatch.match_selectors	call site: 00680	soupsieve.css_match.CSSMatch.match_indeterminate.get_parent_form
13	7	bs4.BeautifulSoup.__init__	call site: 00007	bs4.builder.TreeBuilderRegistry.lookup
11	141	soupsieve.css_parser.CSSParser.parse_selectors	call site: 00141	.print
11	452	soupsieve.css_match._DocumentNav.get_next	call site: 00452	soupsieve.css_match._DocumentNav.is_content_string
9	438	soupsieve.css_match._DocumentNav.is_special_string	call site: 00438	soupsieve.css_match._DocumentNav.is_cdata
8	43	bs4.BeautifulSoup.__init__	call site: 00043	bs4.BeautifulSoup._decode_markup
8	671	soupsieve.css_match.CSSMatch.match_selectors	call site: 00671	soupsieve.css_match._DocumentNav.get_tag_descendants
8	727	soupsieve.css_match.CSSMatch.match_selectors	call site: 00727	soupsieve.css_match.SoupSieve.match

Runtime coverage analysis

Covered functions

337

Functions that are reachable but not covered

155

Reachable functions

254

Percentage of reachable functions covered

38.98%

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
...fuzz_filter	5
bs4	37
bs4.builder	7
bs4.element	4
soupsieve	7
soupsieve.css_parser	80
soupsieve.util	3
soupsieve.css_match	125
soupsieve.css_types	2

Fuzzer: fuzz_select

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	326	45.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	386	54.2%
All colors	712	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
63	521	soupsieve.css_match.CSSMatch.match_selectors	call site: 00521	soupsieve.css_match.Inputs.parse_value
31	673	soupsieve.css_match.CSSMatch.match_selectors	call site: 00673	soupsieve.css_match.CSSMatch.match_dir
20	204	soupsieve.css_parser.CSSParser.parse_pseudo_class	call site: 00204	soupsieve.css_parser.CSSParser.parse_selectors
18	597	soupsieve.css_match.CSSMatch.match_lang	call site: 00597	soupsieve.css_match._DocumentNav.iter_attributes
15	657	soupsieve.css_match.CSSMatch.match_selectors	call site: 00657	soupsieve.css_match.CSSMatch.match_indeterminate.get_parent_form
13	8	bs4.BeautifulSoup.__init__	call site: 00008	bs4.builder.TreeBuilderRegistry.lookup
11	141	soupsieve.css_parser.CSSParser.parse_selectors	call site: 00141	.print
8	44	bs4.BeautifulSoup.__init__	call site: 00044	bs4.BeautifulSoup._decode_markup
8	648	soupsieve.css_match.CSSMatch.match_selectors	call site: 00648	soupsieve.css_match._DocumentNav.get_tag_descendants
7	196	soupsieve.css_parser.CSSParser.parse_pseudo_class	call site: 00196	soupsieve.css_types.SelectorList.__init__
6	26	bs4.builder.TreeBuilderRegistry.lookup	call site: 00026	.len
6	36	bs4.BeautifulSoup.__init__	call site: 00036	warnings.warn

Runtime coverage analysis

Covered functions

337

Functions that are reachable but not covered

137

Reachable functions

237

Percentage of reachable functions covered

42.19%

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
...fuzz_select	5
bs4	37
bs4.builder	7
bs4.element	4
soupsieve	6
soupsieve.css_parser	80
soupsieve.util	3
soupsieve.css_match	111
soupsieve.css_types	2

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.__getattr__	bs4.element	2	['N/A', 'N/A']	11	0	2	2	4	275	0	861	825
bs4.diagnose.diagnose	bs4.diagnose	1	['N/A']	6	0	18	7	6	80	1	291	112
bs4.dammit.EncodingDetector.encodings	bs4.dammit	1	['N/A']	2	0	7	8	6	17	0	60	48
bs4.dammit.UnicodeDammit.__init__	bs4.dammit	8	['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A']	3	0	2	6	5	17	1	59	41

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

Functions statically reachable by fuzzers

178 / 557

Cyclomatic complexity statically reachable by fuzzers

758 / 1974

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

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/fuzz_match.py

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=['soupsieve.css_match.CSSMatch.match_selectors', 'soupsieve.css_parser.CSSParser.parse_pseudo_class', 'soupsieve.css_match.CSSMatch.match_lang', 'bs4.BeautifulSoup.__init__', 'soupsieve.css_parser.CSSParser.parse_selectors']

/src/fuzz_closest.py

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=['soupsieve.css_match.CSSMatch.match_selectors', 'soupsieve.css_parser.CSSParser.parse_pseudo_class', 'soupsieve.css_match.CSSMatch.match_lang', 'bs4.BeautifulSoup.__init__', 'soupsieve.css_parser.CSSParser.parse_selectors']

/src/fuzz_filter.py

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=['soupsieve.css_match.CSSMatch.match_selectors', 'soupsieve.css_parser.CSSParser.parse_pseudo_class', 'soupsieve.css_match.CSSMatch.match_lang', 'bs4.BeautifulSoup.__init__', 'soupsieve.css_parser.CSSParser.parse_selectors', 'soupsieve.css_match._DocumentNav.get_next', 'soupsieve.css_match._DocumentNav.is_special_string']

/src/fuzz_select.py

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=['soupsieve.css_match.CSSMatch.match_selectors', 'soupsieve.css_parser.CSSParser.parse_pseudo_class', 'soupsieve.css_match.CSSMatch.match_lang', 'bs4.BeautifulSoup.__init__', 'soupsieve.css_parser.CSSParser.parse_selectors']

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
soupsieve.css_match.Inputs.parse_value	49	2	4.081%	['fuzz_closest', 'fuzz_select', 'fuzz_filter', 'fuzz_match']
soupsieve.css_match.CSSMatch.extended_language_filter	33	0	0.0%	['fuzz_closest', 'fuzz_select', 'fuzz_filter', 'fuzz_match']
soupsieve.css_match.CSSMatch.match_indeterminate.get_parent_form	47	0	0.0%	['fuzz_closest', 'fuzz_select', 'fuzz_filter', 'fuzz_match']
soupsieve.css_match.CSSMatch.match_lang	63	34	53.96%	['fuzz_closest', 'fuzz_select', 'fuzz_filter', 'fuzz_match']
soupsieve.css_match.CSSMatch.match_dir	39	0	0.0%	['fuzz_closest', 'fuzz_select', 'fuzz_filter', 'fuzz_match']
bs4.element.PageElement.insert	36	18	50.0%	['fuzz_closest', 'fuzz_select', 'fuzz_filter', 'fuzz_match']
bs4.element.SoupStrainer._matches	49	4	8.163%	['fuzz_closest', 'fuzz_select', 'fuzz_filter', 'fuzz_match']
bs4.element.ResultSet.__getattr__	315	106	33.65%	['fuzz_closest', 'fuzz_select', 'fuzz_filter', 'fuzz_match']
bs4.builder._html5lib.TextNode.cloneNode	72	0	0.0%	[]
match.end	40	21	52.5%	['fuzz_filter', 'fuzz_select', 'fuzz_match']
bs4.dammit.chardet_dammit	374	149	39.83%	['fuzz_closest', 'fuzz_select', 'fuzz_filter', 'fuzz_match']
html.parser.attrfind.match	994	51	5.130%	['fuzz_filter', 'fuzz_select', 'fuzz_match']
bs4.builder._lxml.LXMLTreeBuilder.test_fragment_to_document	96	15	15.62%	['fuzz_closest', 'fuzz_select', 'fuzz_filter', 'fuzz_match']

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

Directories in report

Directory