High level conclusions

Fuzzers reach 91.38% of cyclomatic complexity.

Fuzzers reach 86.75% of all functions.

Fuzzers reach 84.43% code coverage.

Reachability and coverage overview

Functions statically reachable by fuzzers

262 / 302

Cyclomatic complexity statically reachable by fuzzers

2228 / 2438

Runtime code coverage of functions

255 / 302

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 following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1	12	uriDissectQueryMallocExMmW	call site: 00012	uriFreeQueryListMmW

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 following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1	12	uriDissectQueryMallocExMmA	call site: 00012	uriFreeQueryListMmA

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_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.7%
gold	[1:9]	48	22.0%
yellow	[10:29]	14	6.42%
greenyellow	[30:49]	11	5.04%
lawngreen	50+	115	52.7%
All colors	218	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
2	13	uriOnExitSegmentNzNcOrScheme2A	call site: 00013	uriStopMallocA
1	18	uriParseSegmentNzNcOrScheme2A	call site: 00018	uriStopSyntaxA
1	26	uriParseMustBeSegmentNzNcA	call site: 00026	uriStopMallocA
1	29	uriParseMustBeSegmentNzNcA	call site: 00029	uriStopMallocA
1	32	uriParseSegmentA	call site: 00032	uriStopSyntaxA
1	34	uriParsePcharA	call site: 00034	uriStopSyntaxA
1	36	uriParseMustBeSegmentNzNcA	call site: 00036	uriStopMallocA
1	40	uriParseZeroMoreSlashSegsA	call site: 00040	uriStopMallocA
1	48	uriParseMustBeSegmentNzNcA	call site: 00048	uriStopMallocA
1	53	uriParseSegmentNzNcOrScheme2A	call site: 00053	uriStopMallocA
1	55	uriParseSegmentNzNcOrScheme2A	call site: 00055	uriStopMallocA
1	64	uriParsePathRootlessA	call site: 00064	uriStopMallocA

Runtime coverage analysis

Covered functions

66

Functions that are reachable but not covered

2

Reachable functions

67

Percentage of reachable functions covered

97.01%

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	4
/src/uriparser/src/UriParseBase.c	2
/src/uriparser/src/UriIp4.c	6
/src/uriparser/src/UriIp4Base.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.7%
gold	[1:9]	48	22.0%
yellow	[10:29]	10	4.58%
greenyellow	[30:49]	8	3.66%
lawngreen	50+	122	55.9%
All colors	218	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
2	13	uriOnExitSegmentNzNcOrScheme2W	call site: 00013	uriStopMallocW
1	18	uriParseSegmentNzNcOrScheme2W	call site: 00018	uriStopSyntaxW
1	26	uriParseMustBeSegmentNzNcW	call site: 00026	uriStopMallocW
1	29	uriParseMustBeSegmentNzNcW	call site: 00029	uriStopMallocW
1	32	uriParseSegmentW	call site: 00032	uriStopSyntaxW
1	34	uriParsePcharW	call site: 00034	uriStopSyntaxW
1	36	uriParseMustBeSegmentNzNcW	call site: 00036	uriStopMallocW
1	40	uriParseZeroMoreSlashSegsW	call site: 00040	uriStopMallocW
1	48	uriParseMustBeSegmentNzNcW	call site: 00048	uriStopMallocW
1	53	uriParseSegmentNzNcOrScheme2W	call site: 00053	uriStopMallocW
1	55	uriParseSegmentNzNcOrScheme2W	call site: 00055	uriStopMallocW
1	64	uriParsePathRootlessW	call site: 00064	uriStopMallocW

Runtime coverage analysis

Covered functions

66

Functions that are reachable but not covered

2

Reachable functions

67

Percentage of reachable functions covered

97.01%

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	4
/src/uriparser/src/UriParseBase.c	2
/src/uriparser/src/UriIp4.c	6
/src/uriparser/src/UriIp4Base.c	2

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	53	13.0%
gold	[1:9]	47	11.5%
yellow	[10:29]	19	4.67%
greenyellow	[30:49]	7	1.72%
lawngreen	50+	280	68.9%
All colors	406	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
3	295	uriNormalizeSyntaxEngineW	call site: 00295	uriFixPercentEncodingInplaceW
2	76	uriOnExitSegmentNzNcOrScheme2W	call site: 00076	uriStopMallocW
2	292	uriNormalizeSyntaxEngineW	call site: 00292	uriPreventLeakageW
2	306	uriNormalizeSyntaxEngineW	call site: 00306	uriDropLeadingZerosInplaceW
2	327	uriNormalizeSyntaxEngineW	call site: 00327	uriFixPercentEncodingInplaceW
1	81	uriParseSegmentNzNcOrScheme2W	call site: 00081	uriStopSyntaxW
1	89	uriParseMustBeSegmentNzNcW	call site: 00089	uriStopMallocW
1	92	uriParseMustBeSegmentNzNcW	call site: 00092	uriStopMallocW
1	95	uriParseSegmentW	call site: 00095	uriStopSyntaxW
1	97	uriParsePcharW	call site: 00097	uriStopSyntaxW
1	99	uriParseMustBeSegmentNzNcW	call site: 00099	uriStopMallocW
1	103	uriParseZeroMoreSlashSegsW	call site: 00103	uriStopMallocW

Runtime coverage analysis

Covered functions

125

Functions that are reachable but not covered

10

Reachable functions

141

Percentage of reachable functions covered

92.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/ParseFuzzer.cpp	7
/src/uriparser/fuzz/FuzzingUtils.h	3
/src/uriparser/src/UriEscape.c	4
/src/uriparser/src/UriCommon.c	13
/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_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	53	13.0%
gold	[1:9]	43	10.5%
yellow	[10:29]	23	5.66%
greenyellow	[30:49]	6	1.47%
lawngreen	50+	281	69.2%
All colors	406	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
3	295	uriNormalizeSyntaxEngineA	call site: 00295	uriFixPercentEncodingInplaceA
2	76	uriOnExitSegmentNzNcOrScheme2A	call site: 00076	uriStopMallocA
2	292	uriNormalizeSyntaxEngineA	call site: 00292	uriLowercaseInplaceA
2	306	uriNormalizeSyntaxEngineA	call site: 00306	uriDropLeadingZerosInplaceA
2	327	uriNormalizeSyntaxEngineA	call site: 00327	uriFixPercentEncodingInplaceA
1	81	uriParseSegmentNzNcOrScheme2A	call site: 00081	uriStopSyntaxA
1	89	uriParseMustBeSegmentNzNcA	call site: 00089	uriStopMallocA
1	92	uriParseMustBeSegmentNzNcA	call site: 00092	uriStopMallocA
1	95	uriParseSegmentA	call site: 00095	uriStopSyntaxA
1	97	uriParsePcharA	call site: 00097	uriStopSyntaxA
1	99	uriParseMustBeSegmentNzNcA	call site: 00099	uriStopMallocA
1	103	uriParseZeroMoreSlashSegsA	call site: 00103	uriStopMallocA

Runtime coverage analysis

Covered functions

125

Functions that are reachable but not covered

10

Reachable functions

141

Percentage of reachable functions covered

92.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/ParseFuzzer.cpp	7
/src/uriparser/fuzz/FuzzingUtils.h	3
/src/uriparser/src/UriEscape.c	4
/src/uriparser/src/UriCommon.c	13
/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']	2	0	12	3	2	2	0	60	54

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

Functions statically reachable by fuzzers

264 / 302

Cyclomatic complexity statically reachable by fuzzers

2282 / 2438

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=['uriOnExitSegmentNzNcOrScheme2A', 'uriParseSegmentNzNcOrScheme2A', 'uriParseMustBeSegmentNzNcA', 'uriParseSegmentA', 'uriParsePcharA', 'uriParseZeroMoreSlashSegsA']

/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/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']

/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']

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

Directories in report

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