High level conclusions

Fuzzers reach 69.84% code coverage.

Fuzzers reach 19.56% of cyclomatic complexity.

Fuzzers reach 30.65% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

61 / 199

Cyclomatic complexity statically reachable by fuzzers

260 / 1329

Runtime code coverage of functions

139 / 199

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

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	13	12.2%
gold	[1:9]	2	1.88%
yellow	[10:29]	3	2.83%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	88	83.0%
All colors	106	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	7	ogg_sync_buffer	call site: 00007	ogg_sync_clear
3	47	ogg_stream_pagein	call site: 00047	ogg_stream_clear
2	97	speex_realloc	call site: 00097	speex_warning
1	24	LLVMFuzzerTestOneInput	call site: 00024	ogg_stream_clear
1	41	ogg_stream_pagein	call site: 00041	ogg_stream_clear
1	43	_os_lacing_expand	call site: 00043	ogg_stream_clear
1	45	_os_lacing_expand	call site: 00045	ogg_stream_clear
1	86	process_header(ogg_packet*, int, int*, int*, int*, int*, int*, SpeexStereoState*, int*)	call site: 00086	speex_decoder_destroy

Runtime coverage analysis

Covered functions

87

Functions that are reachable but not covered

6

Reachable functions

55

Percentage of reachable functions covered

89.09%

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
speex/contrib/oss-fuzz/speexdec_fuzzer.cc	3
oggframing.c	27
speex/libspeex/bits.c	5
speex/libspeex/./os_support.h	5
speex/libspeex/speex.c	4
speex/libspeex/speex_header.c	2
speex/libspeex/modes_wb.c	1
speex/libspeex/stereo.c	1

Fuzzer: speex_encode_fuzzer_float

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	5	10.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	41	89.1%
All colors	46	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	21	speex_encode_stereo_int	call site: 00021	speex_realloc

Runtime coverage analysis

Covered functions

77

Functions that are reachable but not covered

6

Reachable functions

23

Percentage of reachable functions covered

73.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.

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
speex/contrib/oss-fuzz/speexenc_fuzzer.cc	1
speex/libspeex/modes_wb.c	1
speex/libspeex/speex.c	4
speex/libspeex/bits.c	7
speex/libspeex/./os_support.h	5
speex/libspeex/stereo.c	1
speex/libspeex/vq.c	1

Fuzzer: speex_decode_fuzzer_fixed

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	13	11.9%
gold	[1:9]	2	1.83%
yellow	[10:29]	3	2.75%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	91	83.4%
All colors	109	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	7	ogg_sync_buffer	call site: 00007	ogg_sync_clear
3	47	ogg_stream_pagein	call site: 00047	ogg_stream_clear
2	97	speex_realloc	call site: 00097	speex_warning
1	24	LLVMFuzzerTestOneInput	call site: 00024	ogg_stream_clear
1	41	ogg_stream_pagein	call site: 00041	ogg_stream_clear
1	43	_os_lacing_expand	call site: 00043	ogg_stream_clear
1	45	_os_lacing_expand	call site: 00045	ogg_stream_clear
1	86	process_header(ogg_packet*, int, int*, int*, int*, int*, int*, SpeexStereoState*, int*)	call site: 00086	speex_decoder_destroy

Runtime coverage analysis

Covered functions

89

Functions that are reachable but not covered

5

Reachable functions

57

Percentage of reachable functions covered

91.23%

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
speex/contrib/oss-fuzz/speexdec_fuzzer.cc	3
oggframing.c	27
speex/libspeex/bits.c	5
speex/libspeex/./os_support.h	5
speex/libspeex/speex.c	4
speex/libspeex/speex_header.c	2
speex/libspeex/modes_wb.c	1
speex/libspeex/stereo.c	2
speex/libspeex/./math_approx.h	2

Fuzzer: speex_encode_fuzzer_fixed

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	5	10.6%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	42	89.3%
All colors	47	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	21	speex_encode_stereo_int	call site: 00021	speex_realloc

Runtime coverage analysis

Covered functions

76

Functions that are reachable but not covered

5

Reachable functions

23

Percentage of reachable functions covered

78.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
speex/contrib/oss-fuzz/speexenc_fuzzer.cc	1
speex/libspeex/modes_wb.c	1
speex/libspeex/speex.c	4
speex/libspeex/bits.c	7
speex/libspeex/./os_support.h	5
speex/libspeex/stereo.c	1
speex/libspeex/./math_approx.h	1
speex/libspeex/vq.c	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
nb_encode	/src/speex/libspeex/nb_celp.c	3	['N/A', 'N/A', 'N/A']	3	0	2849	340	109	42	0	299	275
nb_decode	/src/speex/libspeex/nb_celp.c	3	['N/A', 'N/A', 'N/A']	4	0	2293	284	97	27	0	219	165
split_cb_search_shape_sign	/src/speex/libspeex/cb_search.c	13	['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'int', 'int', 'N/A', 'N/A', 'N/A', 'N/A', 'int', 'int']	4	0	1164	133	37	18	0	124	89
sb_encode	/src/speex/libspeex/sb_celp.c	3	['N/A', 'N/A', 'N/A']	3	0	2144	205	63	34	0	182	72
sb_decode	/src/speex/libspeex/sb_celp.c	3	['N/A', 'N/A', 'N/A']	3	0	1102	93	30	21	0	102	50
pitch_search_3tap	/src/speex/libspeex/ltp.c	20	['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'int', 'int', 'float', 'int', 'int', 'N/A', 'N/A', 'N/A', 'N/A', 'int', 'int', 'int', 'N/A']	3	0	381	31	11	18	0	101	43

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

Functions statically reachable by fuzzers

119 / 199

Cyclomatic complexity statically reachable by fuzzers

944 / 1329

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.

speex/contrib/oss-fuzz/speexdec_fuzzer.cc

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=['ogg_sync_buffer', 'ogg_stream_pagein', 'speex_realloc', 'LLVMFuzzerTestOneInput', '_os_lacing_expand', 'process_header(ogg_packet*, int, int*, int*, int*, int*, int*, SpeexStereoState*, int*)']

speex/contrib/oss-fuzz/speexenc_fuzzer.cc

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=['speex_encode_stereo_int']

speex/contrib/oss-fuzz/speexdec_fuzzer.cc

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=['ogg_sync_buffer', 'ogg_stream_pagein', 'speex_realloc', 'LLVMFuzzerTestOneInput', '_os_lacing_expand', 'process_header(ogg_packet*, int, int*, int*, int*, int*, int*, SpeexStereoState*, int*)']

speex/contrib/oss-fuzz/speexenc_fuzzer.cc

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=['speex_encode_stereo_int']

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
nb_decoder_ctl	120	55	45.83%	['speex_decode_fuzzer_float', 'speex_decode_fuzzer_fixed']
sb_decoder_ctl	125	57	45.6%	['speex_decode_fuzzer_float', 'speex_decode_fuzzer_fixed']
speex_bits_pack	38	19	50.0%	['speex_encode_fuzzer_float', 'speex_encode_fuzzer_fixed']

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/speex/libspeex/sb_celp.c	[]	[]
/src/speex/libspeex/./vq_sse.h	[]	[]
/src/speex/libspeex/speex_callbacks.c	[]	[]
/src/speex/libspeex/lpc.c	[]	[]
/src/speex/libspeex/stereo.c	['speex_decode_fuzzer_float', 'speex_encode_fuzzer_float', 'speex_decode_fuzzer_fixed', 'speex_encode_fuzzer_fixed']	['speex_decode_fuzzer_float', 'speex_encode_fuzzer_float', 'speex_decode_fuzzer_fixed', 'speex_encode_fuzzer_fixed']
/src/speex/libspeex/modes_wb.c	['speex_decode_fuzzer_float', 'speex_encode_fuzzer_float', 'speex_decode_fuzzer_fixed', 'speex_encode_fuzzer_fixed']	['speex_decode_fuzzer_float', 'speex_encode_fuzzer_float', 'speex_decode_fuzzer_fixed', 'speex_encode_fuzzer_fixed']
/src/speex/libspeex/./ltp_sse.h	[]	[]
/src/speex/libspeex/quant_lsp.c	[]	[]
/src/speex/contrib/oss-fuzz/speexenc_fuzzer.cc	['speex_encode_fuzzer_float', 'speex_encode_fuzzer_fixed']	['speex_encode_fuzzer_float', 'speex_encode_fuzzer_fixed']
/src/speex/libspeex/./math_approx.h	['speex_decode_fuzzer_fixed', 'speex_encode_fuzzer_fixed']	[]
/src/speex/libspeex/speex_header.c	['speex_decode_fuzzer_float', 'speex_decode_fuzzer_fixed']	['speex_decode_fuzzer_float', 'speex_decode_fuzzer_fixed']
/src/speex/libspeex/cb_search.c	[]	[]
/src/speex/libspeex/filters.c	[]	[]
/src/speex/libspeex/./os_support.h	['speex_decode_fuzzer_float', 'speex_encode_fuzzer_float', 'speex_decode_fuzzer_fixed', 'speex_encode_fuzzer_fixed']	[]
/src/speex/libspeex/speex.c	['speex_decode_fuzzer_float', 'speex_encode_fuzzer_float', 'speex_decode_fuzzer_fixed', 'speex_encode_fuzzer_fixed']	['speex_decode_fuzzer_float', 'speex_encode_fuzzer_float', 'speex_decode_fuzzer_fixed', 'speex_encode_fuzzer_fixed']
/src/speex/libspeex/lsp.c	[]	[]
/src/speex/libspeex/bits.c	['speex_decode_fuzzer_float', 'speex_encode_fuzzer_float', 'speex_decode_fuzzer_fixed', 'speex_encode_fuzzer_fixed']	['speex_decode_fuzzer_float', 'speex_encode_fuzzer_float', 'speex_decode_fuzzer_fixed', 'speex_encode_fuzzer_fixed']
/src/speex/libspeex/nb_celp.c	[]	[]
/src/speex/libspeex/./filters_sse.h	[]	[]
/src/speex/libspeex/ltp.c	[]	[]
/src/speex/libspeex/vq.c	['speex_encode_fuzzer_float', 'speex_encode_fuzzer_fixed']	['speex_encode_fuzzer_float', 'speex_encode_fuzzer_fixed']
/src/ogg/src/framing.c	['speex_decode_fuzzer_float', 'speex_decode_fuzzer_fixed']	['speex_decode_fuzzer_float', 'speex_decode_fuzzer_fixed']
/src/speex/libspeex/modes.c	[]	[]
/src/speex/contrib/oss-fuzz/speexdec_fuzzer.cc	['speex_decode_fuzzer_float', 'speex_decode_fuzzer_fixed']	['speex_decode_fuzzer_float', 'speex_decode_fuzzer_fixed']
/src/speex/libspeex/./cb_search_sse.h	[]	[]
/src/speex/libspeex/vbr.c	[]	[]

Directories in report

Directory
/src/speex/libspeex/
/src/speex/contrib/oss-fuzz/
/src/speex/libspeex/./
/src/ogg/src/