High level conclusions

Fuzzers reach 51.83% of cyclomatic complexity.

Fuzzers reach 43.61% of all functions.

Fuzzer fuzzing/FuzzOAuthToken.c is blocked:

The runtime code coverage of fuzzing/FuzzOAuthToken.c covers 5.263% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzzing/FuzzStunAttrAdd.c is blocked:

The runtime code coverage of fuzzing/FuzzStunAttrAdd.c covers 16.66% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzzing/FuzzOAuthRoundTrip.c is blocked:

The runtime code coverage of fuzzing/FuzzOAuthRoundTrip.c covers 3.333% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzzing/FuzzChannelData.c is blocked:

The runtime code coverage of fuzzing/FuzzChannelData.c covers 8.333% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzzing/FuzzStunAddrCodec.c is blocked:

The runtime code coverage of fuzzing/FuzzStunAddrCodec.c covers 20.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Reachability and coverage overview

Functions statically reachable by fuzzers

82 / 188

Cyclomatic complexity statically reachable by fuzzers

494 / 953

Runtime code coverage of functions

30 / 188

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: fuzzing/FuzzStunAddrCodec.c

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	15	93.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	1	6.25%
All colors	16	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
15	0	EP	call site: 00000	stun_addr_decode

Runtime coverage analysis

Covered functions

31

Functions that are reachable but not covered

4

Reachable functions

5

Percentage of reachable functions covered

20.0%

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
fuzzing/FuzzStunAddrCodec.c	1
src/client/ns_turn_msg_addr.c	2

Fuzzer: fuzzing/FuzzChannelData.c

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	22	95.6%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	1	4.34%
All colors	23	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
22	0	EP	call site: 00000	stun_get_message_len_str

Runtime coverage analysis

Covered functions

31

Functions that are reachable but not covered

11

Reachable functions

12

Percentage of reachable functions covered

8.33%

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
fuzzing/FuzzChannelData.c	1
src/client/ns_turn_msg.c	5

Fuzzer: fuzzing/FuzzOAuthRoundTrip.c

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	62	98.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	1	1.58%
All colors	63	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
62	0	EP	call site: 00000	encode_oauth_token

Runtime coverage analysis

Covered functions

31

Functions that are reachable but not covered

29

Reachable functions

30

Percentage of reachable functions covered

3.33%

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
fuzzing/FuzzOAuthRoundTrip.c	1
src/client/ns_turn_msg.c	9
src/ns_turn_defs.h	1

Fuzzer: fuzzing/FuzzStunAttrIter.c

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	106	82.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	1	0.78%
greenyellow	[30:49]	2	1.56%
lawngreen	50+	19	14.8%
All colors	128	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
77	26	stun_attr_get_first_by_type_str	call site: 00026	stun_attr_get_first_addr_str
19	108	stun_is_error_response_str	call site: 00108	stun_is_challenge_response_str
4	15	stun_attr_get_value	call site: 00015	stun_attr_get_next_str
2	12	stun_attr_get_type	call site: 00012	stun_attr_get_value
1	0	EP	call site: 00000	stun_is_command_message_str
1	4	stun_is_command_message_str	call site: 00004	stun_attr_get_first_str
1	10	stun_attr_get_len	call site: 00010	stun_attr_get_type
1	22	stun_attr_get_next_str	call site: 00022	stun_attr_get_first_by_type_str

Runtime coverage analysis

Covered functions

31

Functions that are reachable but not covered

27

Reachable functions

40

Percentage of reachable functions covered

32.5%

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
fuzzing/FuzzStunAttrIter.c	1
src/client/ns_turn_msg.c	27
src/client/ns_turn_ioaddr.c	7
src/client/ns_turn_msg_addr.c	1
src/ns_turn_defs.h	1

Fuzzer: fuzzing/FuzzStunAttrAdd.c

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	65	91.5%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	8.45%
All colors	71	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
61	9	stun_set_command_message_len_str	call site: 00009	stun_attr_add_addr_str
2	4	stun_is_command_message_str	call site: 00004	stun_attr_add_str
1	0	EP	call site: 00000	stun_is_command_message_str
1	7	stun_get_command_message_len_str	call site: 00007	stun_set_command_message_len_str

Runtime coverage analysis

Covered functions

31

Functions that are reachable but not covered

25

Reachable functions

30

Percentage of reachable functions covered

16.67%

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
fuzzing/FuzzStunAttrAdd.c	1
src/client/ns_turn_msg.c	16
src/client/ns_turn_ioaddr.c	5
src/client/ns_turn_msg_addr.c	1

Fuzzer: FuzzStunClient

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	6	12.0%
gold	[1:9]	1	2.0%
yellow	[10:29]	12	24.0%
greenyellow	[30:49]	12	24.0%
lawngreen	50+	19	38.0%
All colors	50	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
5	44	stun_attr_get_next_str	call site: 00044	stun_attr_get_value
1	40	stun_attr_get_first_by_type_str	call site: 00040	stun_attr_get_first_str

Runtime coverage analysis

Covered functions

22

Functions that are reachable but not covered

3

Reachable functions

24

Percentage of reachable functions covered

87.5%

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
fuzzing/FuzzStunClient.c	1
src/apps/common/stun_buffer.c	4
src/client/ns_turn_msg.c	17

Fuzzer: fuzzing/FuzzOldStun.c

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	29	41.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	3	4.28%
greenyellow	[30:49]	6	8.57%
lawngreen	50+	32	45.7%
All colors	70	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
6	53	stun_is_command_message_full_check_str	call site: 00053	stun_is_command_message_full_check_str
5	1	LLVMFuzzerTestOneInput	call site: 00001	stun_is_command_message_str
4	65	stun_is_response_str	call site: 00065	stun_attr_get_next_str
3	43	stun_attr_get_value	call site: 00043	stun_is_command_message_full_check_str
2	13	stun_get_method_str	call site: 00013	stun_is_request_str
2	16	is_channel_msg_str	call site: 00016	stun_is_indication_str
2	40	stun_attr_get_next_str	call site: 00040	stun_attr_get_value
1	9	stun_is_command_message_str	call site: 00009	stun_get_msg_type_str
1	11	stun_get_msg_type_str	call site: 00011	stun_get_method_str
1	20	stun_is_indication_str	call site: 00020	stun_is_success_response_str
1	23	stun_is_success_response_str	call site: 00023	stun_is_error_response_str
1	36	stun_attr_get_first_by_type_str	call site: 00036	stun_attr_get_first_str

Runtime coverage analysis

Covered functions

31

Functions that are reachable but not covered

5

Reachable functions

25

Percentage of reachable functions covered

80.0%

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
fuzzing/FuzzOldStun.c	1
src/client/ns_turn_msg.c	22

Fuzzer: fuzzing/FuzzStunIntegrity.c

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	28	32.5%
gold	[1:9]	4	4.65%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	54	62.7%
All colors	86	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
20	42	stun_produce_integrity_key_str	call site: 00042	EVP_MD_CTX_new
4	73	stun_calculate_hmac	call site: 00073	EVP_sha384
1	0	EP	call site: 00000	stun_is_command_message_full_check_str
1	15	stun_attr_get_first_by_type_str	call site: 00015	stun_attr_get_first_str
1	26	stun_is_command_message_full_check_str	call site: 00026	stun_check_message_integrity_str
1	84	stun_check_message_integrity_by_key_str	call site: 00084	stun_check_message_integrity_str

Runtime coverage analysis

Covered functions

31

Functions that are reachable but not covered

20

Reachable functions

39

Percentage of reachable functions covered

48.72%

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
fuzzing/FuzzStunIntegrity.c	1
src/client/ns_turn_msg.c	18

Fuzzer: FuzzStun

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	25	29.0%
gold	[1:9]	4	4.65%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	57	66.2%
All colors	86	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
20	42	stun_produce_integrity_key_str	call site: 00042	EVP_MD_CTX_new
4	73	stun_calculate_hmac	call site: 00073	EVP_sha384
1	15	stun_attr_get_first_by_type_str	call site: 00015	stun_attr_get_first_str

Runtime coverage analysis

Covered functions

20

Functions that are reachable but not covered

20

Reachable functions

39

Percentage of reachable functions covered

48.72%

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
fuzzing/FuzzStun.c	1
src/client/ns_turn_msg.c	18

Fuzzer: fuzzing/FuzzOAuthToken.c

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	33	97.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	1	2.94%
All colors	34	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
33	0	EP	call site: 00000	decode_oauth_token

Runtime coverage analysis

Covered functions

31

Functions that are reachable but not covered

18

Reachable functions

19

Percentage of reachable functions covered

5.26%

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
fuzzing/FuzzOAuthToken.c	1
src/client/ns_turn_msg.c	4
src/ns_turn_defs.h	1

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
stun_set_binding_response	/src/coturn/src/apps/common/stun_buffer.c	6	['N/A', 'N/A', 'N/A', 'int', 'N/A', 'bool']	8	0	36	3	2	39	0	161	62
convert_oauth_key_data	/src/coturn/src/client/ns_turn_msg.c	4	['N/A', 'N/A', 'N/A', 'size_t']	1	0	345	47	17	10	0	57	51
make_ioa_addr_from_full_string	/src/coturn/src/client/ns_turn_ioaddr.c	3	['N/A', 'short', 'N/A']	2	0	72	12	5	13	0	57	47

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

Functions statically reachable by fuzzers

109 / 188

Cyclomatic complexity statically reachable by fuzzers

636 / 953

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.

fuzzing/FuzzStunAddrCodec.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

fuzzing/FuzzChannelData.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

fuzzing/FuzzOAuthRoundTrip.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

fuzzing/FuzzStunAttrIter.c

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=['stun_attr_get_first_by_type_str', 'stun_is_error_response_str', 'stun_attr_get_value', 'stun_attr_get_type', 'stun_is_command_message_str', 'stun_attr_get_len', 'stun_attr_get_next_str']

fuzzing/FuzzStunAttrAdd.c

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=['stun_set_command_message_len_str', 'stun_is_command_message_str', 'stun_get_command_message_len_str']

fuzzing/FuzzStunClient.c

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=['stun_attr_get_next_str', 'stun_attr_get_first_by_type_str']

fuzzing/FuzzOldStun.c

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=['stun_is_command_message_full_check_str', 'LLVMFuzzerTestOneInput', 'stun_is_response_str', 'stun_attr_get_value', 'stun_get_method_str', 'is_channel_msg_str', 'stun_attr_get_next_str', 'stun_is_command_message_str', 'stun_get_msg_type_str', 'stun_is_indication_str']

fuzzing/FuzzStunIntegrity.c

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=['stun_produce_integrity_key_str', 'stun_calculate_hmac', 'stun_attr_get_first_by_type_str', 'stun_is_command_message_full_check_str', 'stun_check_message_integrity_by_key_str']

fuzzing/FuzzStun.c

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=['stun_produce_integrity_key_str', 'stun_calculate_hmac', 'stun_attr_get_first_by_type_str']

fuzzing/FuzzOAuthToken.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

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
stun_produce_integrity_key_str	65	31	47.69%	['/src/coturn/fuzzing/FuzzOAuthToken.c', '/src/coturn/fuzzing/FuzzOAuthRoundTrip.c', '/src/coturn/fuzzing/FuzzChannelData.c', '/src/coturn/fuzzing/FuzzStunAttrAdd.c', '/src/coturn/fuzzing/FuzzOldStun.c', '/src/coturn/fuzzing/FuzzStunIntegrity.c', '/src/coturn/fuzzing/FuzzStunAttrIter.c', 'FuzzStun', '/src/coturn/fuzzing/FuzzStunAddrCodec.c']

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/coturn/src/client/ns_turn_msg_addr.c	['fuzzing/FuzzStunAddrCodec.c', 'fuzzing/FuzzStunAttrIter.c', 'fuzzing/FuzzStunAttrAdd.c']	[]
/src/coturn/fuzzing/FuzzOpenSSLInit.c	[]	[]
/src/coturn/fuzzing/FuzzChannelData.c	['fuzzing/FuzzChannelData.c']	['fuzzing/FuzzChannelData.c']
/src/coturn/src/client/ns_turn_msg.c	['fuzzing/FuzzChannelData.c', 'fuzzing/FuzzOAuthRoundTrip.c', 'fuzzing/FuzzStunAttrIter.c', 'fuzzing/FuzzStunAttrAdd.c', 'FuzzStunClient', 'fuzzing/FuzzOldStun.c', 'fuzzing/FuzzStunIntegrity.c', 'FuzzStun', 'fuzzing/FuzzOAuthToken.c']	['fuzzing/FuzzChannelData.c', 'fuzzing/FuzzOAuthRoundTrip.c', 'fuzzing/FuzzStunAttrIter.c', 'fuzzing/FuzzStunAttrAdd.c', 'FuzzStunClient', 'fuzzing/FuzzOldStun.c', 'fuzzing/FuzzStunIntegrity.c', 'FuzzStun', 'fuzzing/FuzzOAuthToken.c']
/src/coturn/src/client/ns_turn_ioaddr.c	['fuzzing/FuzzStunAttrIter.c', 'fuzzing/FuzzStunAttrAdd.c']	[]
/src/coturn/fuzzing/FuzzOAuthRoundTrip.c	['fuzzing/FuzzOAuthRoundTrip.c']	['fuzzing/FuzzOAuthRoundTrip.c']
/src/coturn/fuzzing/FuzzStunAttrAdd.c	['fuzzing/FuzzStunAttrAdd.c']	['fuzzing/FuzzStunAttrAdd.c']
/src/coturn/fuzzing/FuzzStunClient.c	['FuzzStunClient']	['FuzzStunClient']
/src/coturn/fuzzing/FuzzOAuthToken.c	['fuzzing/FuzzOAuthToken.c']	['fuzzing/FuzzOAuthToken.c']
/src/coturn/src/apps/common/stun_buffer.c	['FuzzStunClient']	['FuzzStunClient']
/src/coturn/fuzzing/FuzzOldStun.c	['fuzzing/FuzzOldStun.c']	['fuzzing/FuzzOldStun.c']
/src/coturn/fuzzing/FuzzStun.c	['FuzzStun']	['FuzzStun']
/src/coturn/fuzzing/FuzzStunIntegrity.c	['fuzzing/FuzzStunIntegrity.c']	['fuzzing/FuzzStunIntegrity.c']
/src/coturn/fuzzing/FuzzStunAttrIter.c	['fuzzing/FuzzStunAttrIter.c']	['fuzzing/FuzzStunAttrIter.c']
/src/coturn/src/ns_turn_defs.h	['fuzzing/FuzzOAuthRoundTrip.c', 'fuzzing/FuzzStunAttrIter.c', 'fuzzing/FuzzOAuthToken.c']	[]
/src/coturn/fuzzing/FuzzStunAddrCodec.c	['fuzzing/FuzzStunAddrCodec.c']	['fuzzing/FuzzStunAddrCodec.c']

Directories in report

Directory
/src/coturn/src/apps/common/
/src/coturn/src/client/
/src/coturn/fuzzing/
/src/coturn/src/