High level conclusions

Fuzzers reach 71.57% code coverage.

Fuzzers reach 85.55% of cyclomatic complexity.

Fuzzers reach 77.25% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

231 / 299

Cyclomatic complexity statically reachable by fuzzers

2761 / 3227

Runtime code coverage of functions

214 / 299

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	589	84.0%
gold	[1:9]	99	14.1%
yellow	[10:29]	5	0.71%
greenyellow	[30:49]	2	0.28%
lawngreen	50+	6	0.85%
All colors	701	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
445	199	addBackwardRuleWithSingleCell	call site: 00199	compileRule
25	67	parseCharsInternal	call site: 00067	_lou_getALine
17	180	addForwardRuleWithSingleChar	call site: 00180	_lou_logMessage
13	94	getAChar	call site: 00094	_lou_getALine
12	49	compileRule	call site: 00049	compileHyphenation
9	140	getRuleDotsPattern	call site: 00140	compileError
8	646	compileFile	call site: 00646	_lou_logMessage
6	25	rpl_free	call site: 00025	_lou_outOfMemory
5	19	getLogLevelFromEnvironment	call site: 00019	_lou_logMessage
5	128	compileFile	call site: 00128	compileError
5	659	compileTable	call site: 00659	compileFile
4	62	parseCharsInternal	call site: 00062	compileWarning

Runtime coverage analysis

Covered functions

56

Functions that are reachable but not covered

78

Reachable functions

131

Percentage of reachable functions covered

40.46%

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	93
/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	268	30.3%
gold	[1:9]	129	14.5%
yellow	[10:29]	94	10.6%
greenyellow	[30:49]	30	3.39%
lawngreen	50+	363	41.0%
All colors	884	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
17	234	compileGrouping	call site: 00234	compileRule
16	359	compileRule	call site: 00359	compileBrailleIndicator
12	751	_lou_backTranslate	call site: 00751	_lou_outOfMemory
10	650	compileFile	call site: 00650	_lou_logMessage
9	405	compileRule	call site: 00405	getRuleCharsText
8	376	compileRule	call site: 00376	getRuleCharsText
8	396	compileRule	call site: 00396	getRuleCharsText
6	610	compileRule	call site: 00610	allocateCharacterClasses
6	689	finalizeCharacter	call site: 00689	_lou_logMessage
5	123	lou_freeTableFiles	call site: 00123	compileFile
5	132	compileFile	call site: 00132	compileError
5	663	compileTable	call site: 00663	compileFile

Runtime coverage analysis

Covered functions

171

Functions that are reachable but not covered

24

Reachable functions

191

Percentage of reachable functions covered

87.43%

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	100
/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	227	20.8%
gold	[1:9]	107	9.81%
yellow	[10:29]	72	6.60%
greenyellow	[30:49]	29	2.66%
lawngreen	50+	655	60.0%
All colors	1090	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	238	compileRule	call site: 00238	compileRule
10	650	compileFile	call site: 00650	_lou_logMessage
7	689	finalizeCharacter	call site: 00689	_lou_logMessage
6	113	getOpcode	call site: 00113	includeFile
6	913	syllableBreak	call site: 00913	toLowercase
6	990	insertEmphasisEnd	call site: 00990	beginCount
5	123	lou_freeTableFiles	call site: 00123	compileFile
5	132	compileFile	call site: 00132	compileError
5	663	compileTable	call site: 00663	compileFile
4	31	compileError	call site: 00031	_lou_outOfMemory
4	226	compileGrouping	call site: 00226	_lou_outOfMemory
4	310	addCharacterClass	call site: 00310	_lou_outOfMemory

Runtime coverage analysis

Covered functions

204

Functions that are reachable but not covered

40

Reachable functions

238

Percentage of reachable functions covered

83.19%

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	100
/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

263 / 299

Cyclomatic complexity statically reachable by fuzzers

3040 / 3227

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', 'parseCharsInternal', 'addForwardRuleWithSingleChar', 'getAChar', 'compileRule', '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=['compileGrouping', 'compileRule', '_lou_backTranslate', 'compileFile', 'finalizeCharacter', 'lou_freeTableFiles']

/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', 'getOpcode', 'syllableBreak', 'insertEmphasisEnd', 'lou_freeTableFiles', 'compileTable', 'compileError']

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_translate_generic', 'table_fuzzer', '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/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_translate_generic.c	['fuzz_translate_generic']	['fuzz_translate_generic']
/src/liblouis/liblouis/lou_backTranslateString.c	['fuzz_backtranslate']	['fuzz_backtranslate']
/src/liblouis/tests/fuzzing/fuzz_backtranslate.c	['fuzz_backtranslate']	['fuzz_backtranslate']
/src/liblouis/tools/gnulib/free.c	['table_fuzzer', 'fuzz_backtranslate', 'fuzz_translate_generic']	['table_fuzzer', '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/liblouis/utils.c	['table_fuzzer', 'fuzz_backtranslate', 'fuzz_translate_generic']	['table_fuzzer', 'fuzz_backtranslate', 'fuzz_translate_generic']
/src/liblouis/liblouis/./internal.h	['table_fuzzer', 'fuzz_backtranslate', 'fuzz_translate_generic']	[]
/src/liblouis/liblouis/pattern.c	['table_fuzzer', 'fuzz_backtranslate', 'fuzz_translate_generic']	['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/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']

Directories in report

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