High level conclusions

Fuzzers reach 93.15% of cyclomatic complexity.

Fuzzers reach 88.73% of all functions.

Fuzzers reach 86.34% code coverage.

Reachability and coverage overview

Functions statically reachable by fuzzers

260 / 293

Cyclomatic complexity statically reachable by fuzzers

2247 / 2412

Runtime code coverage of functions

253 / 293

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: uri_dissect_query_mallocw_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	1	3.33%
gold	[1:9]	1	3.33%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	28	93.3%
All colors	30	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
0	0	None	0	36	uriEscapeExW	call site: 00020	/src/uriparser/src/UriEscape.c:105
0	0	None	0	36	uriEscapeExW	call site: 00020	/src/uriparser/src/UriEscape.c:191
0	0	None	0	36	uriEscapeExW	call site: 00020	/src/uriparser/src/UriEscape.c:211
0	0	None	0	4	uriUnescapeInPlaceExW	call site: 00010	/src/uriparser/src/UriEscape.c:426
0	0	None	0	0	uriAppendQueryItemW	call site: 00007	/src/uriparser/src/UriQuery.c:317
0	0	None	0	0	uriAppendQueryItemW	call site: 00008	/src/uriparser/src/UriQuery.c:337

Runtime coverage analysis

Covered functions

20

Functions that are reachable but not covered

2

Reachable functions

22

Percentage of reachable functions covered

90.91%

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/uriparser/fuzz/DissectQueryMallocFuzzer.cpp	1
/src/uriparser/fuzz/FuzzingUtils.h	2
/src/uriparser/src/UriQuery.c	11
/src/uriparser/src/UriMemory.c	1
/src/uriparser/src/UriEscape.c	2
/src/uriparser/src/UriCommon.c	2

Fuzzer: uri_dissect_query_malloc_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	1	3.33%
gold	[1:9]	1	3.33%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	28	93.3%
All colors	30	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
0	0	None	0	36	uriEscapeExA	call site: 00020	/src/uriparser/src/UriEscape.c:105
0	0	None	0	36	uriEscapeExA	call site: 00020	/src/uriparser/src/UriEscape.c:191
0	0	None	0	36	uriEscapeExA	call site: 00020	/src/uriparser/src/UriEscape.c:211
0	0	None	0	4	uriUnescapeInPlaceExA	call site: 00010	/src/uriparser/src/UriEscape.c:426
0	0	None	0	0	uriAppendQueryItemA	call site: 00007	/src/uriparser/src/UriQuery.c:317
0	0	None	0	0	uriAppendQueryItemA	call site: 00008	/src/uriparser/src/UriQuery.c:337

Runtime coverage analysis

Covered functions

20

Functions that are reachable but not covered

2

Reachable functions

22

Percentage of reachable functions covered

90.91%

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/uriparser/fuzz/DissectQueryMallocFuzzer.cpp	1
/src/uriparser/fuzz/FuzzingUtils.h	2
/src/uriparser/src/UriQuery.c	11
/src/uriparser/src/UriMemory.c	1
/src/uriparser/src/UriEscape.c	2
/src/uriparser/src/UriCommon.c	2

Fuzzer: uri_freew_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	30	13.8%
gold	[1:9]	51	23.5%
yellow	[10:29]	8	3.68%
greenyellow	[30:49]	7	3.22%
lawngreen	50+	121	55.7%
All colors	217	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
37	37	1 : View List ['uriStopMallocW']	37	37	uriParseSegmentNzNcOrScheme2W	call site: 00054	/src/uriparser/src/UriParse.c:1899
37	37	1 : View List ['uriStopMallocW']	37	37	uriParseSegmentNzNcOrScheme2W	call site: 00205	/src/uriparser/src/UriParse.c:1923
37	37	1 : View List ['uriStopMallocW']	37	37	uriParsePathRootlessW	call site: 00063	/src/uriparser/src/UriParse.c:1509
37	37	1 : View List ['uriStopMallocW']	37	37	uriParseMustBeSegmentNzNcW	call site: 00025	/src/uriparser/src/UriParse.c:895
37	37	1 : View List ['uriStopMallocW']	37	37	uriParseMustBeSegmentNzNcW	call site: 00035	/src/uriparser/src/UriParse.c:947
37	37	1 : View List ['uriStopMallocW']	37	37	uriParseMustBeSegmentNzNcW	call site: 00047	/src/uriparser/src/UriParse.c:960
37	37	1 : View List ['uriStopMallocW']	37	37	uriParseIpLit2W	call site: 00084	/src/uriparser/src/UriParse.c:568
37	37	1 : View List ['uriStopMallocW']	37	37	uriParseOwnHost2W	call site: 00179	/src/uriparser/src/UriParse.c:1067
37	37	1 : View List ['uriStopMallocW']	37	37	uriParsePathAbsNoLeadSlashW	call site: 00201	/src/uriparser/src/UriParse.c:1484
0	0	None	37	37	uriParseSegmentNzNcOrScheme2W	call site: 00052	/src/uriparser/src/UriParse.c:1894
0	0	None	37	37	uriParseMustBeSegmentNzNcW	call site: 00028	/src/uriparser/src/UriParse.c:938
0	0	None	0	1234	uriParseIPv6address2W	call site: 00086	/src/uriparser/src/UriParse.c:600

Runtime coverage analysis

Covered functions

65

Functions that are reachable but not covered

2

Reachable functions

66

Percentage of reachable functions covered

96.97%

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/uriparser/fuzz/FreeFuzzer.cpp	1
/src/uriparser/fuzz/FuzzingUtils.h	2
/src/uriparser/src/UriParse.c	46
/src/uriparser/src/UriMemory.c	1
/src/uriparser/src/UriCommon.c	3
/src/uriparser/src/UriParseBase.c	2
/src/uriparser/src/UriIp4.c	6
/src/uriparser/src/UriIp4Base.c	2

Fuzzer: uri_free_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	30	13.8%
gold	[1:9]	43	19.8%
yellow	[10:29]	19	8.75%
greenyellow	[30:49]	14	6.45%
lawngreen	50+	111	51.1%
All colors	217	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
37	37	1 : View List ['uriStopMallocA']	37	37	uriParseSegmentNzNcOrScheme2A	call site: 00054	/src/uriparser/src/UriParse.c:1899
37	37	1 : View List ['uriStopMallocA']	37	37	uriParseSegmentNzNcOrScheme2A	call site: 00205	/src/uriparser/src/UriParse.c:1923
37	37	1 : View List ['uriStopMallocA']	37	37	uriParsePathRootlessA	call site: 00063	/src/uriparser/src/UriParse.c:1509
37	37	1 : View List ['uriStopMallocA']	37	37	uriParseMustBeSegmentNzNcA	call site: 00025	/src/uriparser/src/UriParse.c:895
37	37	1 : View List ['uriStopMallocA']	37	37	uriParseMustBeSegmentNzNcA	call site: 00035	/src/uriparser/src/UriParse.c:947
37	37	1 : View List ['uriStopMallocA']	37	37	uriParseMustBeSegmentNzNcA	call site: 00047	/src/uriparser/src/UriParse.c:960
37	37	1 : View List ['uriStopMallocA']	37	37	uriParseIpLit2A	call site: 00084	/src/uriparser/src/UriParse.c:568
37	37	1 : View List ['uriStopMallocA']	37	37	uriParseOwnHost2A	call site: 00179	/src/uriparser/src/UriParse.c:1067
37	37	1 : View List ['uriStopMallocA']	37	37	uriParsePathAbsNoLeadSlashA	call site: 00201	/src/uriparser/src/UriParse.c:1484
0	0	None	37	37	uriParseSegmentNzNcOrScheme2A	call site: 00052	/src/uriparser/src/UriParse.c:1894
0	0	None	37	37	uriParseMustBeSegmentNzNcA	call site: 00028	/src/uriparser/src/UriParse.c:938
0	0	None	0	1234	uriParseIPv6address2A	call site: 00086	/src/uriparser/src/UriParse.c:600

Runtime coverage analysis

Covered functions

65

Functions that are reachable but not covered

2

Reachable functions

66

Percentage of reachable functions covered

96.97%

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/uriparser/fuzz/FreeFuzzer.cpp	1
/src/uriparser/fuzz/FuzzingUtils.h	2
/src/uriparser/src/UriParse.c	46
/src/uriparser/src/UriMemory.c	1
/src/uriparser/src/UriCommon.c	3
/src/uriparser/src/UriParseBase.c	2
/src/uriparser/src/UriIp4.c	6
/src/uriparser/src/UriIp4Base.c	2

Fuzzer: uri_parse_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	52	12.8%
gold	[1:9]	44	10.8%
yellow	[10:29]	20	4.95%
greenyellow	[30:49]	3	0.74%
lawngreen	50+	285	70.5%
All colors	404	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
37	37	1 : View List ['uriStopMallocA']	37	37	uriParseSegmentNzNcOrScheme2A	call site: 00117	/src/uriparser/src/UriParse.c:1899
37	37	1 : View List ['uriStopMallocA']	37	37	uriParseSegmentNzNcOrScheme2A	call site: 00244	/src/uriparser/src/UriParse.c:1923
37	37	1 : View List ['uriStopMallocA']	37	37	uriParsePathRootlessA	call site: 00126	/src/uriparser/src/UriParse.c:1509
37	37	1 : View List ['uriStopMallocA']	37	37	uriParseMustBeSegmentNzNcA	call site: 00088	/src/uriparser/src/UriParse.c:895
37	37	1 : View List ['uriStopMallocA']	37	37	uriParseMustBeSegmentNzNcA	call site: 00098	/src/uriparser/src/UriParse.c:947
37	37	1 : View List ['uriStopMallocA']	37	37	uriParseMustBeSegmentNzNcA	call site: 00110	/src/uriparser/src/UriParse.c:960
37	37	1 : View List ['uriStopMallocA']	37	37	uriParseIpLit2A	call site: 00147	/src/uriparser/src/UriParse.c:568
37	37	1 : View List ['uriStopMallocA']	37	37	uriParseOwnHost2A	call site: 00218	/src/uriparser/src/UriParse.c:1067
37	37	1 : View List ['uriStopMallocA']	37	37	uriParsePathAbsNoLeadSlashA	call site: 00240	/src/uriparser/src/UriParse.c:1484
17	17	1 : View List ['uriPreventLeakageA']	17	17	uriNormalizeSyntaxEngineA	call site: 00330	/src/uriparser/src/UriNormalize.c:868
0	0	None	394	789	uriNormalizeSyntaxEngineA	call site: 00286	/src/uriparser/src/UriNormalize.c:670
0	0	None	284	643	uriNormalizeSyntaxEngineA	call site: 00295	/src/uriparser/src/UriNormalize.c:701

Runtime coverage analysis

Covered functions

124

Functions that are reachable but not covered

10

Reachable functions

140

Percentage of reachable functions covered

92.86%

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/uriparser/fuzz/ParseFuzzer.cpp	7
/src/uriparser/fuzz/FuzzingUtils.h	3
/src/uriparser/src/UriEscape.c	4
/src/uriparser/src/UriCommon.c	12
/src/uriparser/src/UriFile.c	6
/src/uriparser/src/UriIp4.c	6
/src/uriparser/src/UriIp4Base.c	2
/src/uriparser/src/UriParse.c	49
/src/uriparser/src/UriMemory.c	1
/src/uriparser/src/UriParseBase.c	2
/src/uriparser/src/UriRecompose.c	2
/src/uriparser/src/UriCompare.c	1
/src/uriparser/src/UriNormalize.c	19
/src/uriparser/src/UriNormalizeBase.c	1
/src/uriparser/src/UriResolve.c	6
/src/uriparser/src/UriShorten.c	5

Fuzzer: uri_parsew_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	52	12.8%
gold	[1:9]	49	12.1%
yellow	[10:29]	15	3.71%
greenyellow	[30:49]	7	1.73%
lawngreen	50+	281	69.5%
All colors	404	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
37	37	1 : View List ['uriStopMallocW']	37	37	uriParseSegmentNzNcOrScheme2W	call site: 00117	/src/uriparser/src/UriParse.c:1899
37	37	1 : View List ['uriStopMallocW']	37	37	uriParseSegmentNzNcOrScheme2W	call site: 00244	/src/uriparser/src/UriParse.c:1923
37	37	1 : View List ['uriStopMallocW']	37	37	uriParsePathRootlessW	call site: 00126	/src/uriparser/src/UriParse.c:1509
37	37	1 : View List ['uriStopMallocW']	37	37	uriParseMustBeSegmentNzNcW	call site: 00088	/src/uriparser/src/UriParse.c:895
37	37	1 : View List ['uriStopMallocW']	37	37	uriParseMustBeSegmentNzNcW	call site: 00098	/src/uriparser/src/UriParse.c:947
37	37	1 : View List ['uriStopMallocW']	37	37	uriParseMustBeSegmentNzNcW	call site: 00110	/src/uriparser/src/UriParse.c:960
37	37	1 : View List ['uriStopMallocW']	37	37	uriParseIpLit2W	call site: 00147	/src/uriparser/src/UriParse.c:568
37	37	1 : View List ['uriStopMallocW']	37	37	uriParseOwnHost2W	call site: 00218	/src/uriparser/src/UriParse.c:1067
37	37	1 : View List ['uriStopMallocW']	37	37	uriParsePathAbsNoLeadSlashW	call site: 00240	/src/uriparser/src/UriParse.c:1484
17	17	1 : View List ['uriPreventLeakageW']	17	17	uriNormalizeSyntaxEngineW	call site: 00330	/src/uriparser/src/UriNormalize.c:868
0	0	None	389	807	uriNormalizeSyntaxEngineW	call site: 00286	/src/uriparser/src/UriNormalize.c:670
0	0	None	296	670	uriNormalizeSyntaxEngineW	call site: 00295	/src/uriparser/src/UriNormalize.c:701

Runtime coverage analysis

Covered functions

124

Functions that are reachable but not covered

10

Reachable functions

140

Percentage of reachable functions covered

92.86%

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/uriparser/fuzz/ParseFuzzer.cpp	7
/src/uriparser/fuzz/FuzzingUtils.h	3
/src/uriparser/src/UriEscape.c	4
/src/uriparser/src/UriCommon.c	12
/src/uriparser/src/UriFile.c	6
/src/uriparser/src/UriIp4.c	6
/src/uriparser/src/UriIp4Base.c	2
/src/uriparser/src/UriParse.c	49
/src/uriparser/src/UriMemory.c	1
/src/uriparser/src/UriParseBase.c	2
/src/uriparser/src/UriRecompose.c	2
/src/uriparser/src/UriCompare.c	1
/src/uriparser/src/UriNormalize.c	19
/src/uriparser/src/UriNormalizeBase.c	1
/src/uriparser/src/UriResolve.c	6
/src/uriparser/src/UriShorten.c	5

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
uriTestMemoryManager	/src/uriparser/src/UriMemory.c	1	['N/A']	1	0	698	101	49	1	0	55	49

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

Functions statically reachable by fuzzers

261 / 293

Cyclomatic complexity statically reachable by fuzzers

2296 / 2412

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/uriparser/fuzz/DissectQueryMallocFuzzer.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=['uriDissectQueryMallocExMmW']

/src/uriparser/fuzz/DissectQueryMallocFuzzer.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=['uriDissectQueryMallocExMmA']

/src/uriparser/fuzz/FreeFuzzer.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=['uriOnExitSegmentNzNcOrScheme2W', 'uriParseSegmentNzNcOrScheme2W', 'uriParseMustBeSegmentNzNcW', 'uriParseSegmentW', 'uriParsePcharW', 'uriParseZeroMoreSlashSegsW']

/src/uriparser/fuzz/FreeFuzzer.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=['uriOnExitSegmentNzNcOrScheme2A', 'uriParseSegmentNzNcOrScheme2A', 'uriParseMustBeSegmentNzNcA', 'uriParseSegmentA', 'uriParsePcharA', 'uriParseZeroMoreSlashSegsA']

/src/uriparser/fuzz/ParseFuzzer.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=['uriNormalizeSyntaxEngineA', 'uriOnExitSegmentNzNcOrScheme2A', 'uriParseSegmentNzNcOrScheme2A', 'uriParseMustBeSegmentNzNcA', 'uriParseSegmentA', 'uriParsePcharA']

/src/uriparser/fuzz/ParseFuzzer.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=['uriNormalizeSyntaxEngineW', 'uriOnExitSegmentNzNcOrScheme2W', 'uriParseSegmentNzNcOrScheme2W', 'uriParseMustBeSegmentNzNcW', 'uriParseSegmentW', 'uriParsePcharW']

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
uriMakeOwnerEngineA	59	21	35.59%	['uri_parse_fuzzer']
uriMakeOwnerEngineW	59	21	35.59%	['uri_parsew_fuzzer']

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/uriparser/src/UriRecompose.c	['uri_parse_fuzzer', 'uri_parsew_fuzzer']	['uri_parse_fuzzer', 'uri_parsew_fuzzer']
/src/uriparser/fuzz/FuzzingUtils.h	['uri_dissect_query_mallocw_fuzzer', 'uri_dissect_query_malloc_fuzzer', 'uri_freew_fuzzer', 'uri_free_fuzzer', 'uri_parse_fuzzer', 'uri_parsew_fuzzer']	['uri_dissect_query_mallocw_fuzzer', 'uri_dissect_query_malloc_fuzzer', 'uri_freew_fuzzer', 'uri_free_fuzzer', 'uri_parse_fuzzer', 'uri_parsew_fuzzer']
/src/uriparser/src/UriResolve.c	['uri_parse_fuzzer', 'uri_parsew_fuzzer']	['uri_parse_fuzzer', 'uri_parsew_fuzzer']
/src/uriparser/src/UriIp4Base.c	['uri_freew_fuzzer', 'uri_free_fuzzer', 'uri_parse_fuzzer', 'uri_parsew_fuzzer']	['uri_freew_fuzzer', 'uri_free_fuzzer', 'uri_parse_fuzzer', 'uri_parsew_fuzzer']
/src/uriparser/src/UriCompare.c	['uri_parse_fuzzer', 'uri_parsew_fuzzer']	['uri_parse_fuzzer', 'uri_parsew_fuzzer']
/src/uriparser/src/UriCommon.c	['uri_dissect_query_mallocw_fuzzer', 'uri_dissect_query_malloc_fuzzer', 'uri_freew_fuzzer', 'uri_free_fuzzer', 'uri_parse_fuzzer', 'uri_parsew_fuzzer']	['uri_dissect_query_mallocw_fuzzer', 'uri_dissect_query_malloc_fuzzer', 'uri_freew_fuzzer', 'uri_free_fuzzer', 'uri_parse_fuzzer', 'uri_parsew_fuzzer']
/src/uriparser/src/UriNormalizeBase.c	['uri_parse_fuzzer', 'uri_parsew_fuzzer']	['uri_parse_fuzzer', 'uri_parsew_fuzzer']
/src/uriparser/src/UriFile.c	['uri_parse_fuzzer', 'uri_parsew_fuzzer']	['uri_parse_fuzzer', 'uri_parsew_fuzzer']
/src/uriparser/src/UriIp4.c	['uri_freew_fuzzer', 'uri_free_fuzzer', 'uri_parse_fuzzer', 'uri_parsew_fuzzer']	['uri_freew_fuzzer', 'uri_free_fuzzer', 'uri_parse_fuzzer', 'uri_parsew_fuzzer']
/src/uriparser/src/UriParse.c	['uri_freew_fuzzer', 'uri_free_fuzzer', 'uri_parse_fuzzer', 'uri_parsew_fuzzer']	['uri_freew_fuzzer', 'uri_free_fuzzer', 'uri_parse_fuzzer', 'uri_parsew_fuzzer']
/src/uriparser/src/UriMemory.c	['uri_dissect_query_mallocw_fuzzer', 'uri_dissect_query_malloc_fuzzer', 'uri_freew_fuzzer', 'uri_free_fuzzer', 'uri_parse_fuzzer', 'uri_parsew_fuzzer']	['uri_dissect_query_mallocw_fuzzer', 'uri_dissect_query_malloc_fuzzer', 'uri_freew_fuzzer', 'uri_free_fuzzer', 'uri_parse_fuzzer', 'uri_parsew_fuzzer']
/src/uriparser/src/UriNormalize.c	['uri_parse_fuzzer', 'uri_parsew_fuzzer']	['uri_parse_fuzzer', 'uri_parsew_fuzzer']
/src/uriparser/fuzz/DissectQueryMallocFuzzer.cpp	['uri_dissect_query_mallocw_fuzzer', 'uri_dissect_query_malloc_fuzzer']	['uri_dissect_query_mallocw_fuzzer', 'uri_dissect_query_malloc_fuzzer']
/usr/local/bin/../include/c++/v1/stdexcept	[]	[]
/src/uriparser/src/UriShorten.c	['uri_parse_fuzzer', 'uri_parsew_fuzzer']	['uri_parse_fuzzer', 'uri_parsew_fuzzer']
/src/uriparser/src/UriQuery.c	['uri_dissect_query_mallocw_fuzzer', 'uri_dissect_query_malloc_fuzzer']	['uri_dissect_query_mallocw_fuzzer', 'uri_dissect_query_malloc_fuzzer']
/src/uriparser/src/UriParseBase.c	['uri_freew_fuzzer', 'uri_free_fuzzer', 'uri_parse_fuzzer', 'uri_parsew_fuzzer']	['uri_freew_fuzzer', 'uri_free_fuzzer', 'uri_parse_fuzzer', 'uri_parsew_fuzzer']
/src/uriparser/src/UriEscape.c	['uri_dissect_query_mallocw_fuzzer', 'uri_dissect_query_malloc_fuzzer', 'uri_parse_fuzzer', 'uri_parsew_fuzzer']	['uri_dissect_query_mallocw_fuzzer', 'uri_dissect_query_malloc_fuzzer', 'uri_parse_fuzzer', 'uri_parsew_fuzzer']
/src/uriparser/fuzz/ParseFuzzer.cpp	['uri_parse_fuzzer', 'uri_parsew_fuzzer']	['uri_parse_fuzzer', 'uri_parsew_fuzzer']
/src/uriparser/fuzz/FreeFuzzer.cpp	['uri_freew_fuzzer', 'uri_free_fuzzer']	['uri_freew_fuzzer', 'uri_free_fuzzer']

Directories in report

Directory
/src/uriparser/src/
/src/uriparser/fuzz/
/usr/local/bin/../include/c++/v1/