High level conclusions

Fuzzer fuzz_backoff is blocked:

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

Fuzzer fuzz_func is blocked:

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

Fuzzer fuzz_helper is blocked:

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

Fuzzer fuzz_encoder is blocked:

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

Fuzzer fuzz_util is blocked:

The runtime code coverage of fuzz_util covers 0.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

26 / 1866

Cyclomatic complexity statically reachable by fuzzers

83 / 6227

Runtime code coverage of functions

33 / 1866

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

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	11	33.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	22	66.6%
All colors	33	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
4	3	...fuzz_util.TestInput	call site: 00003	redis.utils.str_if_bytes
2	17	...fuzz_util.TestInput	call site: 00017	fdp.ConsumeString
2	21	...fuzz_util.TestInput	call site: 00021	fdp.ConsumeString
2	25	...fuzz_util.TestInput	call site: 00025	.set
1	28	redis.utils.merge_result	call site: 00028	.list

Runtime coverage analysis

Covered functions

45

Functions that are reachable but not covered

19

Reachable functions

19

Percentage of reachable functions covered

0.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
/	1
...fuzz_util	10
redis.utils	8

Fuzzer: fuzz_encoder

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	17	50.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	17	50.0%
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
8	5	...fuzz_encoder.TestInput	call site: 00005	.isinstance
6	21	...fuzz_encoder.TestInput	call site: 00021	redis._parsers.encoders.Encoder.decode
3	29	...fuzz_encoder.TestInput	call site: 00029	redis._parsers.encoders.Encoder.decode

Runtime coverage analysis

Covered functions

45

Functions that are reachable but not covered

15

Reachable functions

16

Percentage of reachable functions covered

6.25%

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
/	1
...fuzz_encoder	9
redis._parsers.encoders	6

Fuzzer: fuzz_helper

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	72.6%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	20	27.3%
All colors	73	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
30	42	redis.commands.helpers.parse_to_list	call site: 00042	redis.commands.helpers.decode_dict_keys
9	32	...fuzz_helper.TestInput	call site: 00032	redis.commands.helpers.parse_to_list
6	16	...fuzz_helper.TestInput	call site: 00016	redis.commands.helpers.list_or_args
5	23	redis.commands.helpers.list_or_args	call site: 00023	redis.commands.helpers.list_or_args
3	6	...fuzz_helper.TestInput	call site: 00006	fdp.ConsumeString

Runtime coverage analysis

Covered functions

44

Functions that are reachable but not covered

28

Reachable functions

29

Percentage of reachable functions covered

3.45%

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
/	1
...fuzz_helper	13
redis.commands.helpers	16

Fuzzer: fuzz_func

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	54	72.9%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	20	27.0%
All colors	74	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
49	24	...fuzz_func.TestInput	call site: 00024	redis.client.CaseInsensitiveDict.update
3	20	...fuzz_func.TestInput	call site: 00020	fdp.ConsumeFloat
2	7	...fuzz_func.TestInput	call site: 00007	fdp.ConsumeString

Runtime coverage analysis

Covered functions

44

Functions that are reachable but not covered

16

Reachable functions

16

Percentage of reachable functions covered

0.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
/	1
...fuzz_func	12
redis.client	4

Fuzzer: fuzz_backoff

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	20	45.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	24	54.5%
All colors	44	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
9	34	...fuzz_backoff.TestInput	call site: 00034	redis.backoff.DecorrelatedJitterBackoff.compute
4	10	...fuzz_backoff.TestInput	call site: 00010	redis.backoff.DecorrelatedJitterBackoff.reset
2	16	...fuzz_backoff.TestInput	call site: 00016	.min
2	23	...fuzz_backoff.TestInput	call site: 00023	.min
2	31	...fuzz_backoff.TestInput	call site: 00031	.min
1	7	...fuzz_backoff.TestInput	call site: 00007	.super

Runtime coverage analysis

Covered functions

45

Functions that are reachable but not covered

19

Reachable functions

19

Percentage of reachable functions covered

0.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
/	1
...fuzz_backoff	14
redis.backoff	4

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
redis.commands.search.commands.SearchCommands.sugadd	redis.commands.search.commands	4	['N/A', 'N/A', 'N/A', 'N/A']	19	0	5	2	4	212	0	725	683
redis.cluster.RedisCluster._internal_execute_command	redis.cluster	3	['N/A', 'N/A', 'N/A']	19	0	2	6	5	177	1	595	208
redis.connection.SSLConnection._wrap_socket_with_ssl	redis.connection	2	['N/A', 'N/A']	3	0	11	10	7	57	1	185	182
redis.commands.search.commands.SearchCommands.search	redis.commands.search.commands	3	['N/A', 'N/A', 'N/A']	15	0	1	2	4	164	0	561	102
redis._parsers.resp3._RESP3Parser._read_response	redis._parsers.resp3	3	['N/A', 'N/A', 'N/A']	4	0	0	17	10	26	2	99	81
redis.client.PubSub.on_connect	redis.client	2	['N/A', 'N/A']	16	0	7	3	4	146	0	488	64
redis.asyncio.lock.Lock.acquire	redis.asyncio.lock	4	['N/A', 'N/A', 'N/A', 'N/A']	11	0	2	7	6	151	1	514	64

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

Functions statically reachable by fuzzers

222 / 1866

Cyclomatic complexity statically reachable by fuzzers

848 / 6227

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/fuzz_util.py

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=['...fuzz_util.TestInput', 'redis.utils.merge_result']

/src/fuzz_encoder.py

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=['...fuzz_encoder.TestInput']

/src/fuzz_helper.py

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=['redis.commands.helpers.parse_to_list', '...fuzz_helper.TestInput', 'redis.commands.helpers.list_or_args']

/src/fuzz_func.py

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=['...fuzz_func.TestInput']

/src/fuzz_backoff.py

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=['...fuzz_backoff.TestInput']

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
k.startswith	126	32	25.39%	['fuzz_backoff', 'fuzz_encoder', 'fuzz_util', 'fuzz_func']
re.findall	1913	441	23.05%	['fuzz_encoder', 'fuzz_helper', 'fuzz_backoff', 'fuzz_func', 'fuzz_util']
redis._parsers.commands.CommandsParser.get_keys	32	0	0.0%	[]
redis._parsers.commands.AsyncCommandsParser.get_keys	32	0	0.0%	[]
r.items	980	209	21.32%	['fuzz_backoff', 'fuzz_func', 'fuzz_util', 'fuzz_helper']
n.to_string	666	159	23.87%	['fuzz_encoder', 'fuzz_helper', 'fuzz_backoff', 'fuzz_func', 'fuzz_util']
socket.socket	99	28	28.28%	['fuzz_backoff', 'fuzz_func', 'fuzz_util', 'fuzz_helper']
token.get_value	83	38	45.78%	['fuzz_encoder', 'fuzz_helper', 'fuzz_backoff', 'fuzz_func', 'fuzz_util']
client.register_script	643	154	23.95%	['fuzz_util']
f.redis_args	101	52	51.48%	['fuzz_encoder', 'fuzz_helper', 'fuzz_backoff', 'fuzz_func', 'fuzz_util']
event.pubsub_connection.get_protocol	213	107	50.23%	['fuzz_encoder', 'fuzz_helper', 'fuzz_backoff', 'fuzz_func', 'fuzz_util']
sentinel.execute_command	175	41	23.42%	['fuzz_backoff', 'fuzz_func', 'fuzz_util', 'fuzz_helper']

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
	[]	[]
redis.commands.vectorset.utils	[]	[]
redis.commands.search	[]	[]
redis.backoff	['fuzz_backoff']	[]
redis.commands.helpers	['fuzz_helper']	[]
redis.commands.search.dialect	[]	[]
redis.commands.search.aggregation	[]	[]
hashlib	[]	[]
redis.cache	[]	[]
redis.auth.err	[]	[]
base64	[]	[]
redis.commands.bf.info	[]	[]
redis._parsers.encoders	['fuzz_encoder']	[]
redis.commands.bf	[]	[]
warnings	[]	[]
urllib	[]	[]
redis.commands.search.query	[]	[]
redis.commands.timeseries.utils	[]	[]
logging	[]	[]
uuid	[]	[]
atheris	[]	[]
redis.asyncio.lock	[]	[]
redis.exceptions	[]	[]
json	[]	[]
redis._parsers.socket	[]	[]
...fuzz_helper	['fuzz_helper']	[]
io	[]	[]
redis.asyncio.connection	[]	[]
redis.commands.search.commands	[]	[]
...fuzz_util	['fuzz_util']	[]
itertools	[]	[]
redis.cluster	[]	[]
redis.sentinel	[]	[]
redis.commands	[]	[]
redis.commands.json.path	[]	[]
inspect	[]	[]
redis.typing	[]	[]
functools	[]	[]
redis.commands.timeseries.info	[]	[]
redis.commands.json.decoders	[]	[]
redis._parsers.helpers	[]	[]
...fuzz_encoder	['fuzz_encoder']	[]
redis.commands.core	[]	[]
redis.utils	['fuzz_util']	[]
redis.commands.search.querystring	[]	[]
requests	[]	[]
redis.event	[]	[]
redis._parsers.resp3	[]	[]
redis.commands.vectorset.commands	[]	[]
queue	[]	[]
redis._parsers.hiredis	[]	[]
redis.auth.token_manager	[]	[]
asyncio	[]	[]
time	[]	[]
redis.commands.json	[]	[]
hiredis	[]	[]
redis.asyncio.cluster	[]	[]
redis.commands.search.reducers	[]	[]
redis.credentials	[]	[]
redis.commands.sentinel	[]	[]
redis.asyncio.retry	[]	[]
redis.auth.token	[]	[]
redis.commands.bf.commands	[]	[]
copy	[]	[]
redis.auth	[]	[]
datetime	[]	[]
sys	[]	[]
redis.asyncio.client	[]	[]
textwrap	[]	[]
typing	[]	[]
redis	[]	[]
redis.commands.timeseries.commands	[]	[]
cryptography	[]	[]
redis.commands.cluster	[]	[]
redis.commands.search.document	[]	[]
jwt	[]	[]
weakref	[]	[]
redis.commands.vectorset	[]	[]
binascii	[]	[]
...fuzz_backoff	['fuzz_backoff']	[]
redis.commands.timeseries	[]	[]
collections	[]	[]
redis.connection	[]	[]
redis.commands.search.index_definition	[]	[]
socket	[]	[]
redis._parsers.resp2	[]	[]
redis.auth.idp	[]	[]
os	[]	[]
redis.commands.redismodules	[]	[]
redis.asyncio	[]	[]
re	[]	[]
redis.asyncio.utils	[]	[]
redis.crc	[]	[]
redis.commands.search._util	[]	[]
redis.lock	[]	[]
redis.commands.search.result	[]	[]
redis.asyncio.sentinel	[]	[]
redis.commands.search.field	[]	[]
	[]	[]
async_timeout	[]	[]
threading	[]	[]
redis.commands.json.commands	[]	[]
...fuzz_func	['fuzz_func']	[]
ssl	[]	[]
redis.ocsp	[]	[]
random	[]	[]
types	[]	[]
redis.client	['fuzz_func']	[]
importlib	[]	[]
redis.commands.json._util	[]	[]
redis.retry	[]	[]
redis.commands.search.suggestion	[]	[]
redis._parsers.base	[]	[]
redis._parsers.commands	[]	[]
OpenSSL	[]	[]
redis.commands.search.profile_information	[]	[]
redis._parsers	[]	[]

Directories in report

Directory