High level conclusions

Fuzzers reach 71.18% code coverage.

Fuzzers reach 85.50% of cyclomatic complexity.

Fuzzers reach 76.94% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

227 / 295

Cyclomatic complexity statically reachable by fuzzers

2749 / 3215

Runtime code coverage of functions

210 / 295

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: table_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	585	84.0%
gold	[1:9]	98	14.0%
yellow	[10:29]	5	0.71%
greenyellow	[30:49]	2	0.28%
lawngreen	50+	6	0.86%
All colors	696	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
442	197	addBackwardRuleWithSingleCell	call site: 00197	compileRule
25	65	parseChars	call site: 00065	_lou_getALine
17	178	addForwardRuleWithSingleChar	call site: 00178	_lou_logMessage
15	49	compileRule	call site: 00049	compileHyphenation
13	92	getAChar	call site: 00092	_lou_getALine
9	138	getRuleDotsPattern	call site: 00138	compileError
8	641	compileFile	call site: 00641	_lou_logMessage
6	25	rpl_free	call site: 00025	_lou_outOfMemory
5	19	getLogLevelFromEnvironment	call site: 00019	_lou_logMessage
5	126	compileFile	call site: 00126	compileError
5	654	compileTable	call site: 00654	compileFile
4	668	freeTranslationTable	call site: 00668	freeDisplayTable

Runtime coverage analysis

Covered functions

54

Functions that are reachable but not covered

76

Reachable functions

127

Percentage of reachable functions covered

40.16%

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/liblouis/tests/fuzzing/table_fuzzer.cc	1
/src/liblouis/liblouis/compileTranslationTable.c	89
/src/liblouis/liblouis/logging.c	4
/src/liblouis/tools/gnulib/free.c	1
/src/liblouis/liblouis/utils.c	5
/src/liblouis/liblouis/./internal.h	1
/src/liblouis/liblouis/pattern.c	8
/src/liblouis/liblouis/metadata.c	2

Fuzzer: fuzz_backtranslate

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	420	47.7%
gold	[1:9]	140	15.9%
yellow	[10:29]	61	6.93%
greenyellow	[30:49]	12	1.36%
lawngreen	50+	246	27.9%
All colors	879	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
38	211	compileRule	call site: 00211	compileRule
35	348	compileRule	call site: 00348	compileBrailleIndicator
28	390	compileRule	call site: 00390	compileBrailleIndicator
28	578	compilePassOpcode	call site: 00578	addRule
18	428	compileRule	call site: 00428	addRule
17	684	finalizeCharacter	call site: 00684	_lou_logMessage
13	318	compileRule	call site: 00318	compileBrailleIndicator
12	182	addForwardRuleWithSingleChar	call site: 00182	_lou_logMessage
12	746	_lou_backTranslate	call site: 00746	_lou_outOfMemory
10	645	compileFile	call site: 00645	_lou_logMessage
9	777	back_selectRule	call site: 00777	findBrailleIndicatorRule
7	802	back_selectRule	call site: 00802	isEndWord

Runtime coverage analysis

Covered functions

156

Functions that are reachable but not covered

35

Reachable functions

187

Percentage of reachable functions covered

81.28%

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/liblouis/tests/fuzzing/fuzz_backtranslate.c	2
/src/liblouis/liblouis/logging.c	5
/src/liblouis/liblouis/compileTranslationTable.c	96
/src/liblouis/tools/gnulib/free.c	1
/src/liblouis/liblouis/utils.c	7
/src/liblouis/liblouis/./internal.h	1
/src/liblouis/liblouis/pattern.c	15
/src/liblouis/liblouis/metadata.c	2
/src/liblouis/liblouis/lou_backTranslateString.c	37
/src/liblouis/liblouis/commonTranslationFunctions.c	3

Fuzzer: fuzz_translate_generic

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	185	17.0%
gold	[1:9]	102	9.40%
yellow	[10:29]	51	4.70%
greenyellow	[30:49]	36	3.31%
lawngreen	50+	711	65.5%
All colors	1085	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
13	236	compileRule	call site: 00236	compileRule
10	645	compileFile	call site: 00645	_lou_logMessage
6	684	finalizeCharacter	call site: 00684	_lou_logMessage
6	908	syllableBreak	call site: 00908	toLowercase
6	985	insertEmphasisEnd	call site: 00985	beginCount
5	121	lou_freeTableFiles	call site: 00121	compileFile
5	130	compileFile	call site: 00130	compileError
5	658	compileTable	call site: 00658	compileFile
4	31	compileError	call site: 00031	_lou_outOfMemory
4	224	compileGrouping	call site: 00224	_lou_outOfMemory
4	307	addCharacterClass	call site: 00307	_lou_outOfMemory
4	752	_lou_allocMem	call site: 00752	_lou_outOfMemory

Runtime coverage analysis

Covered functions

205

Functions that are reachable but not covered

35

Reachable functions

234

Percentage of reachable functions covered

85.04%

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/liblouis/tests/fuzzing/fuzz_translate_generic.c	2
/src/liblouis/liblouis/logging.c	6
/src/liblouis/liblouis/compileTranslationTable.c	96
/src/liblouis/tools/gnulib/free.c	1
/src/liblouis/liblouis/utils.c	8
/src/liblouis/liblouis/./internal.h	1
/src/liblouis/liblouis/pattern.c	15
/src/liblouis/liblouis/metadata.c	2
/src/liblouis/liblouis/lou_translateString.c	74
/src/liblouis/liblouis/commonTranslationFunctions.c	3

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
lou_findTables	/src/liblouis/liblouis/metadata.c	1	['N/A']	10	0	156	20	7	58	0	333	256
_lou_defaultTableResolver	/src/liblouis/liblouis/compileTranslationTable.c	2	['N/A', 'N/A']	5	0	218	36	12	20	0	91	41

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

Functions statically reachable by fuzzers

259 / 295

Cyclomatic complexity statically reachable by fuzzers

3028 / 3215

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/liblouis/tests/fuzzing/table_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=['addBackwardRuleWithSingleCell', 'parseChars', 'addForwardRuleWithSingleChar', 'compileRule', 'getAChar', 'getRuleDotsPattern', 'compileFile', 'rpl_free', 'getLogLevelFromEnvironment']

/src/liblouis/tests/fuzzing/fuzz_backtranslate.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=['compileRule', 'compilePassOpcode', 'finalizeCharacter', 'addForwardRuleWithSingleChar', '_lou_backTranslate', 'compileFile']

/src/liblouis/tests/fuzzing/fuzz_translate_generic.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=['compileRule', 'compileFile', 'finalizeCharacter', 'syllableBreak', 'insertEmphasisEnd', 'lou_freeTableFiles', 'compileTable', 'compileError', 'compileGrouping']

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
getLogLevelFromEnvironment	35	5	14.28%	['fuzz_backtranslate', 'table_fuzzer', 'fuzz_translate_generic']
handleMultind	49	3	6.122%	['fuzz_backtranslate']
insertEmphasesAt	71	28	39.43%	['fuzz_translate_generic']
hyphenateWord	56	12	21.42%	['fuzz_translate_generic']

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/liblouis/tests/fuzzing/table_fuzzer.cc	['table_fuzzer']	['table_fuzzer']
/src/liblouis/liblouis/logging.c	['table_fuzzer', 'fuzz_backtranslate', 'fuzz_translate_generic']	['table_fuzzer', 'fuzz_backtranslate', 'fuzz_translate_generic']
/src/liblouis/liblouis/lou_translateString.c	['fuzz_translate_generic']	['fuzz_translate_generic']
/src/liblouis/liblouis/pattern.c	['table_fuzzer', 'fuzz_backtranslate', 'fuzz_translate_generic']	['fuzz_backtranslate', 'fuzz_translate_generic']
/src/liblouis/liblouis/compileTranslationTable.c	['table_fuzzer', 'fuzz_backtranslate', 'fuzz_translate_generic']	['table_fuzzer', 'fuzz_backtranslate', 'fuzz_translate_generic']
/src/liblouis/tests/fuzzing/fuzz_translate_generic.c	['fuzz_translate_generic']	['fuzz_translate_generic']
/src/liblouis/liblouis/utils.c	['table_fuzzer', 'fuzz_backtranslate', 'fuzz_translate_generic']	['table_fuzzer', 'fuzz_backtranslate', 'fuzz_translate_generic']
/src/liblouis/liblouis/metadata.c	['table_fuzzer', 'fuzz_backtranslate', 'fuzz_translate_generic']	['table_fuzzer', 'fuzz_backtranslate', 'fuzz_translate_generic']
/src/liblouis/liblouis/commonTranslationFunctions.c	['fuzz_backtranslate', 'fuzz_translate_generic']	['fuzz_backtranslate', 'fuzz_translate_generic']
/usr/local/bin/../include/c++/v1/stdexcept	[]	[]
/src/liblouis/tests/fuzzing/fuzz_backtranslate.c	['fuzz_backtranslate']	['fuzz_backtranslate']
/src/liblouis/liblouis/lou_backTranslateString.c	['fuzz_backtranslate']	['fuzz_backtranslate']
/src/liblouis/liblouis/./internal.h	['table_fuzzer', 'fuzz_backtranslate', 'fuzz_translate_generic']	[]
/src/liblouis/tools/gnulib/free.c	['table_fuzzer', 'fuzz_backtranslate', 'fuzz_translate_generic']	['table_fuzzer', 'fuzz_backtranslate', 'fuzz_translate_generic']

Directories in report

Directory
/src/liblouis/tools/gnulib/
/src/liblouis/liblouis/
/src/liblouis/tests/fuzzing/
/src/liblouis/liblouis/./
/usr/local/bin/../include/c++/v1/