High level conclusions

Fuzzer raw_deserialize is blocked:

The runtime code coverage of raw_deserialize 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 decode is blocked:

The runtime code coverage of decode covers 25.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 iterate is blocked:

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

Fuzzer raw_deserialize_utf8_lossy is blocked:

The runtime code coverage of raw_deserialize_utf8_lossy 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.

Fuzzers reach 2.059% of cyclomatic complexity.

Fuzzers reach 0.968% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

11 / 1136

Cyclomatic complexity statically reachable by fuzzers

22 / 1068

Runtime code coverage of functions

363 / 1136

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

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	493	100.%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	0	0.0%
All colors	493	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
492	0	EP	call site: 00000	RawElement::try_into

Runtime coverage analysis

Covered functions

2

Functions that are reachable but not covered

3

Reachable functions

3

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.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzz/fuzz_targets/raw_deserialize_utf8_lossy.rs	3
src/ser.rs	8
src/decimal128.rs	67
src/document.rs	10
src/raw/iter.rs	12
src/raw/array.rs	4
src/raw/bson_ref.rs	22
src/raw/array_buf.rs	2
src/oid.rs	2
src/raw/document.rs	16
src/serde_helpers.rs	2
src/error.rs	6
src/raw.rs	28
src/bson.rs	2
src/raw/serde/seeded_visitor.rs	6
src/uuid.rs	6
src/ser/serde.rs	19
src/ser/raw.rs	1
src/tests/serde.rs	7
src/tests/modules/lock.rs	2
src/datetime.rs	1
src/extjson/de.rs	20
src/spec.rs	2

Fuzzer: iterate

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	308	63.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	2	0.41%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	176	36.2%
All colors	486	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
122	141	Timestamp::from_le_bytes	call site: 00141	RawElement::try_into
93	34	RawElement::get_oid_at	call site: 00034	RawElement::try_into
25	378	usize_try_from_i32	call site: 00378	RawElement::try_into
16	0	EP	call site: 00000	RawDocument::decode_from_bytes
8	477	i32_from_slice	call site: 00477	RawDocument::new_unchecked
6	17	i32_from_slice	call site: 00017
6	128	Timestamp::from_le_bytes	call site: 00128	ParsedDecimal128::new
3	350	RawElement::value	call site: 00350	RawElement::try_into
3	446	RawElement::value	call site: 00446
2	266	RawElement::get_oid_at	call site: 00266	RawElement::try_into
2	314	RawElement::value	call site: 00314	RawArray::from_doc
2	339	RawElement::value	call site: 00339

Runtime coverage analysis

Covered functions

110

Functions that are reachable but not covered

14

Reachable functions

18

Percentage of reachable functions covered

22.22%

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
fuzz/fuzz_targets/iterate.rs	2
src/raw/document.rs	16
src/serde_helpers.rs	2
src/document.rs	10
src/error.rs	6
src/raw.rs	28
src/raw/iter.rs	12
src/decimal128.rs	67
src/raw/array.rs	4
src/raw/bson_ref.rs	22
src/raw/array_buf.rs	2
src/oid.rs	2
src/ser.rs	8
src/uuid.rs	6
src/ser/serde.rs	19
src/bson.rs	2
src/raw/serde/seeded_visitor.rs	6
src/ser/raw.rs	1
src/tests/serde.rs	7
src/tests/modules/lock.rs	2
src/datetime.rs	1
src/extjson/de.rs	20
src/spec.rs	2

Fuzzer: string_handling

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	316	63.9%
gold	[1:9]	0	0.0%
yellow	[10:29]	2	0.40%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	176	35.6%
All colors	494	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
122	141	Timestamp::from_le_bytes	call site: 00141	RawElement::try_into
93	34	RawElement::get_oid_at	call site: 00034	RawElement::try_into
25	378	usize_try_from_i32	call site: 00378	RawElement::try_into
16	0	EP	call site: 00000	RawDocument::decode_from_bytes
16	477	i32_from_slice	call site: 00477	RawElement::try_into
6	17	i32_from_slice	call site: 00017
6	128	Timestamp::from_le_bytes	call site: 00128	ParsedDecimal128::new
3	350	RawElement::value	call site: 00350	RawElement::try_into
3	446	RawElement::value	call site: 00446
2	266	RawElement::get_oid_at	call site: 00266	RawElement::try_into
2	314	RawElement::value	call site: 00314	RawArray::from_doc
2	339	RawElement::value	call site: 00339

Runtime coverage analysis

Covered functions

108

Functions that are reachable but not covered

16

Reachable functions

24

Percentage of reachable functions covered

33.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
fuzz/fuzz_targets/string_handling.rs	8
src/raw/document.rs	16
src/serde_helpers.rs	2
src/document.rs	10
src/error.rs	6
src/raw.rs	28
src/raw/iter.rs	12
src/decimal128.rs	67
src/raw/array.rs	5
src/raw/bson_ref.rs	22
src/raw/array_buf.rs	2
src/oid.rs	2
src/ser.rs	8
src/uuid.rs	6
src/ser/serde.rs	19
src/bson.rs	2
src/raw/serde/seeded_visitor.rs	6
src/ser/raw.rs	1
src/tests/serde.rs	7
src/tests/modules/lock.rs	2
src/datetime.rs	1
src/extjson/de.rs	20
src/spec.rs	2

Fuzzer: type_markers

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	312	63.6%
gold	[1:9]	0	0.0%
yellow	[10:29]	2	0.40%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	176	35.9%
All colors	490	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
122	141	Timestamp::from_le_bytes	call site: 00141	RawElement::try_into
93	34	RawElement::get_oid_at	call site: 00034	RawElement::try_into
25	378	usize_try_from_i32	call site: 00378	RawElement::try_into
16	0	EP	call site: 00000	RawDocument::decode_from_bytes
12	477	i32_from_slice	call site: 00477	RawElement::try_into
6	17	i32_from_slice	call site: 00017
6	128	Timestamp::from_le_bytes	call site: 00128	ParsedDecimal128::new
3	350	RawElement::value	call site: 00350	RawElement::try_into
3	446	RawElement::value	call site: 00446
2	266	RawElement::get_oid_at	call site: 00266	RawElement::try_into
2	314	RawElement::value	call site: 00314	RawArray::from_doc
2	339	RawElement::value	call site: 00339

Runtime coverage analysis

Covered functions

108

Functions that are reachable but not covered

14

Reachable functions

21

Percentage of reachable functions covered

33.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
fuzz/fuzz_targets/type_markers.rs	5
src/raw/document.rs	16
src/serde_helpers.rs	2
src/document.rs	10
src/error.rs	6
src/raw.rs	28
src/raw/iter.rs	12
src/decimal128.rs	67
src/raw/array.rs	5
src/raw/bson_ref.rs	22
src/raw/array_buf.rs	2
src/oid.rs	2
src/ser.rs	8
src/uuid.rs	6
src/ser/serde.rs	19
src/bson.rs	2
src/raw/serde/seeded_visitor.rs	6
src/ser/raw.rs	1
src/tests/serde.rs	7
src/tests/modules/lock.rs	2
src/datetime.rs	1
src/extjson/de.rs	20
src/spec.rs	2

Fuzzer: encoding

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	304	55.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	4	0.73%
greenyellow	[30:49]	2	0.36%
lawngreen	50+	235	43.1%
All colors	545	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
81	141	Timestamp::from_le_bytes	call site: 00141	RawElement::try_into
55	72	Document::len	call site: 00072	RawElement::try_into
29	500	RawDocumentBuf::new	call site: 00500	RawElement::try_into
25	378	usize_try_from_i32	call site: 00378	RawElement::try_into
17	54	RawDocumentBuf::decode_from_bytes	call site: 00054	ParsedDecimal128::new
15	477	i32_from_slice	call site: 00477	RawDocumentBuf::try_from
10	228	RawBsonRef::to_raw_bson	call site: 00228
7	0	EP	call site: 00000	RawDocument::decode_from_bytes
7	9	Document::len	call site: 00009	ElementType::from
6	17	i32_from_slice	call site: 00017
6	128	Timestamp::from_le_bytes	call site: 00128	ParsedDecimal128::new
6	249	RawBsonRef::to_raw_bson	call site: 00249

Runtime coverage analysis

Covered functions

373

Functions that are reachable but not covered

18

Reachable functions

39

Percentage of reachable functions covered

53.85%

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
fuzz/fuzz_targets/encoding.rs	14
src/raw/document.rs	16
src/serde_helpers.rs	2
src/document.rs	10
src/error.rs	6
src/raw.rs	28
src/raw/iter.rs	12
src/decimal128.rs	70
src/raw/array.rs	4
src/raw/bson_ref.rs	22
src/raw/array_buf.rs	5
src/oid.rs	2
src/ser.rs	8
src/uuid.rs	6
src/ser/serde.rs	19
src/bson.rs	3
src/raw/serde/seeded_visitor.rs	6
src/ser/raw.rs	1
src/tests/serde.rs	7
src/tests/modules/lock.rs	2
src/datetime.rs	1
src/extjson/de.rs	23
src/spec.rs	2
src/raw/document_buf.rs	6

Fuzzer: decode

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	315	58.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	4	0.74%
greenyellow	[30:49]	2	0.37%
lawngreen	50+	219	40.5%
All colors	540	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
87	107	RawDocumentBuf::decode_from_bytes	call site: 00107	RawElement::try_into
46	455	Timestamp::from_le_bytes	call site: 00455	RawElement::try_into
31	6	Timestamp::from_le_bytes	call site: 00006	RawElement::try_into
28	509	RawDocumentBuf::new	call site: 00509	RawElement::try_into
25	354	usize_try_from_i32	call site: 00354	RawElement::try_into
14	63	RawDocumentBuf::decode_from_bytes	call site: 00063	ElementType::from
11	94	i32_from_slice	call site: 00094	RawDocument::new_unchecked
10	200	RawBsonRef::to_raw_bson	call site: 00200
6	78	i32_from_slice	call site: 00078
6	221	RawBsonRef::to_raw_bson	call site: 00221
6	446	RawElement::value	call site: 00446	RawElement::try_into
5	0	EP	call site: 00000	Document::decode_from_reader

Runtime coverage analysis

Covered functions

357

Functions that are reachable but not covered

6

Reachable functions

8

Percentage of reachable functions covered

25.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
fuzz/fuzz_targets/decode.rs	6
src/document.rs	14
src/raw.rs	28
src/bson.rs	3
src/raw/serde/seeded_visitor.rs	6
src/decimal128.rs	70
src/raw/iter.rs	12
src/raw/array.rs	4
src/raw/bson_ref.rs	22
src/raw/array_buf.rs	6
src/oid.rs	2
src/ser.rs	8
src/raw/document.rs	16
src/serde_helpers.rs	3
src/error.rs	6
src/uuid.rs	6
src/ser/serde.rs	19
src/tests/serde.rs	7
src/tests/modules/lock.rs	2
src/datetime.rs	1
src/extjson/de.rs	20
src/spec.rs	2
src/ser/raw.rs	1
src/de.rs	6
src/raw/document_buf.rs	6

Fuzzer: raw_deserialize

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	278	56.3%
gold	[1:9]	6	1.21%
yellow	[10:29]	2	0.40%
greenyellow	[30:49]	2	0.40%
lawngreen	50+	205	41.5%
All colors	493	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
70	102	Timestamp::from_le_bytes	call site: 00102	RawElement::try_into
57	219	Serializer::new	call site: 00219	RawElement::try_into
32	173	SerializerHint::take	call site: 00173	RawElement::try_into
25	391	usize_try_from_i32	call site: 00391	RawElement::try_into
24	39	RawElement::get_oid_at	call site: 00039	RawElement::value
7	64	Document::len	call site: 00064	ElementType::from
6	72	i32_from_slice	call site: 00072
6	89	Timestamp::from_le_bytes	call site: 00089	ParsedDecimal128::new
6	383	read_len	call site: 00383
5	487	ParsedDecimal128::new	call site: 00487
3	0	EP	call site: 00000
3	80	i32_from_slice	call site: 00080	RawElement::try_into

Runtime coverage analysis

Covered functions

1895

Functions that are reachable but not covered

3

Reachable functions

3

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
fuzz/fuzz_targets/raw_deserialize.rs	3
src/ser.rs	8
src/decimal128.rs	67
src/document.rs	10
src/raw/iter.rs	12
src/raw/array.rs	4
src/raw/bson_ref.rs	22
src/raw/array_buf.rs	2
src/oid.rs	2
src/raw/document.rs	16
src/serde_helpers.rs	2
src/error.rs	6
src/raw.rs	28
src/bson.rs	2
src/raw/serde/seeded_visitor.rs	6
src/uuid.rs	6
src/ser/serde.rs	19
src/ser/raw.rs	1
src/tests/serde.rs	7
src/tests/modules/lock.rs	2
src/datetime.rs	1
src/extjson/de.rs	20
src/spec.rs	2

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

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

Functions statically reachable by fuzzers

11 / 1136

Cyclomatic complexity statically reachable by fuzzers

22 / 1068

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.

fuzz/fuzz_targets/raw_deserialize_utf8_lossy.rs

Dictionary

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

fuzz/fuzz_targets/iterate.rs

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=['Timestamp::from_le_bytes', 'RawElement::get_oid_at', 'usize_try_from_i32', 'i32_from_slice', 'RawElement::value']

fuzz/fuzz_targets/string_handling.rs

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=['Timestamp::from_le_bytes', 'RawElement::get_oid_at', 'usize_try_from_i32', 'i32_from_slice', 'RawElement::value']

fuzz/fuzz_targets/type_markers.rs

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=['Timestamp::from_le_bytes', 'RawElement::get_oid_at', 'usize_try_from_i32', 'i32_from_slice', 'RawElement::value']

fuzz/fuzz_targets/encoding.rs

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=['Timestamp::from_le_bytes', 'Document::len', 'RawDocumentBuf::new', 'usize_try_from_i32', 'RawDocumentBuf::decode_from_bytes', 'i32_from_slice', 'RawBsonRef::to_raw_bson']

fuzz/fuzz_targets/decode.rs

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=['RawDocumentBuf::decode_from_bytes', 'Timestamp::from_le_bytes', 'RawDocumentBuf::new', 'usize_try_from_i32', 'i32_from_slice', 'RawBsonRef::to_raw_bson']

fuzz/fuzz_targets/raw_deserialize.rs

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=['Timestamp::from_le_bytes', 'Serializer::new', 'SerializerHint::take', 'usize_try_from_i32', 'RawElement::get_oid_at', 'Document::len', 'i32_from_slice', 'read_len', 'ParsedDecimal128::new']

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
bson::de::serde::BsonVisitor as serde::de::Visitor::visit_map::bson::de::raw::RegexAccess	121	21	17.35%
bson::de::serde::BsonVisitor as serde::de::Visitor::visit_map::bson::de::raw::BinaryAccess	121	18	14.87%
bson::de::serde::BsonVisitor as serde::de::Visitor::visit_map::bson::de::raw::RawBsonAccess	121	41	33.88%
bson::de::serde::BsonVisitor as serde::de::Visitor::visit_map::bson::de::raw::DateTimeAccess	121	25	20.66%
bson::de::serde::BsonVisitor as serde::de::Visitor::visit_map::bson::de::raw::ObjectIdAccess	121	16	13.22%
bson::de::serde::BsonVisitor as serde::de::Visitor::visit_map::bson::de::raw::DbPointerAccess	121	23	19.00%
bson::de::serde::BsonVisitor as serde::de::Visitor::visit_map::bson::de::raw::TimestampAccess	121	23	19.00%
bson::de::serde::BsonVisitor as serde::de::Visitor::visit_map::bson::de::raw::CodeWithScopeAccess	121	24	19.83%
bson::de::serde::BsonVisitor as serde::de::Visitor::visit_map::bson::de::raw::Decimal128Access	121	30	24.79%
&mut bson::ser::raw::value_serializer::ValueSerializer as serde::ser::SerializeStruct::serialize_field::bson::oid::ObjectId	88	10	11.36%
&mut bson::ser::raw::value_serializer::ValueSerializer as serde::ser::SerializeStruct::serialize_field::bson::document::Document	88	10	11.36%
&mut bson::ser::raw::value_serializer::ValueSerializer as serde::ser::SerializeStruct::serialize_field::alloc::string::String	88	29	32.95%
&mut bson::ser::raw::value_serializer::ValueSerializer as serde::ser::SerializeStruct::serialize_field::serde_bytes::bytes::Bytes	88	11	12.5%
&mut bson::ser::raw::value_serializer::ValueSerializer as serde::ser::SerializeStruct::serialize_field::bson::extjson::models::BinaryBody	88	10	11.36%
&mut bson::ser::raw::value_serializer::ValueSerializer as serde::ser::SerializeStruct::serialize_field::bson::extjson::models::DateTimeBody	88	10	11.36%
&mut bson::ser::raw::value_serializer::ValueSerializer as serde::ser::SerializeStruct::serialize_field::bson::extjson::models::TimestampBody	88	10	11.36%
&mut bson::ser::raw::value_serializer::ValueSerializer as serde::ser::SerializeStruct::serialize_field::bson::extjson::models::TimestampBody as serde::ser::Serialize::serialize::__SerializeWith	88	10	11.36%
&mut bson::ser::raw::value_serializer::ValueSerializer as serde::ser::SerializeStruct::serialize_field::bson::raw::bson_ref::RawRegexRef as serde::ser::Serialize::serialize::BorrowedRegexBody	88	10	11.36%
&mut bson::ser::raw::value_serializer::ValueSerializer as serde::ser::SerializeStruct::serialize_field::bson::raw::bson_ref::RawDbPointerRef as serde::ser::Serialize::serialize::BorrowedDbPointerBody	88	10	11.36%
&mut bson::ser::raw::value_serializer::ValueSerializer as serde::ser::SerializeStruct::serialize_field::&str	88	14	15.90%
&mut bson::ser::raw::value_serializer::ValueSerializer as serde::ser::SerializeStruct::serialize_field::bool	88	10	11.36%
&mut bson::ser::raw::value_serializer::ValueSerializer as serde::ser::SerializeStruct::serialize_field::i32	88	13	14.77%

New fuzzers

The below fuzzers are templates and suggestions for how to target the set of optimal functions above

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/bson-rust/src/ser/raw.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	['iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']
/src/bson-rust/src/tests/serde_helpers.rs	[]	[]
/src/bson-rust/src/datetime.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	['iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']
/src/bson-rust/src/raw/document.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	['iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']
/src/bson-rust/serde-tests/json.rs	[]	[]
/src/bson-rust/src/raw/serde/bson_visitor.rs	[]	[]
/src/bson-rust/src/macros.rs	[]	[]
/src/bson-rust/src/uuid.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	['iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']
/src/bson-rust/src/binary.rs	[]	[]
/src/bson-rust/src/raw/iter.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	['iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']
/src/bson-rust/src/tests/serde.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	['iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']
/src/bson-rust/src/error/uuid.rs	[]	[]
/src/bson-rust/fuzz/fuzz_targets/type_markers.rs	['type_markers']	[]
/src/bson-rust/serde-tests/test.rs	[]	[]
/src/bson-rust/fuzz/fuzz_targets/encoding.rs	['encoding']	['encoding']
/src/bson-rust/src/serde_helpers.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	['iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']
/src/bson-rust/src/raw/test/append.rs	[]	[]
/src/bson-rust/src/spec.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	['iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']
/src/bson-rust/src/tests/modules/serializer_deserializer.rs	[]	[]
/src/bson-rust/src/raw/document_buf.rs	['encoding', 'decode']	['encoding', 'decode']
/src/bson-rust/src/tests/datetime.rs	[]	[]
/src/bson-rust/src/tests/modules/oid.rs	[]	[]
/src/bson-rust/fuzz/fuzz_targets/raw_deserialize_utf8_lossy.rs	['raw_deserialize_utf8_lossy']	[]
/src/bson-rust/src/binary/vector.rs	[]	[]
/src/bson-rust/src/tests/modules/binary.rs	[]	[]
/src/bson-rust/src/raw/test/props.rs	[]	[]
/src/bson-rust/fuzz/fuzz_targets/iterate.rs	['iterate']	[]
/src/bson-rust/src/tests/spec.rs	[]	[]
/src/bson-rust/src/ser.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	[]
/src/bson-rust/src/raw/document_buf/raw_writer.rs	[]	[]
/src/bson-rust/src/error/value_access.rs	[]	[]
/src/bson-rust/src/de.rs	['decode']	[]
/src/bson-rust/src/tests/spec/corpus.rs	[]	[]
/src/bson-rust/src/datetime/builder.rs	[]	[]
/src/bson-rust/src/base64.rs	[]	[]
/src/bson-rust/src/uuid/test.rs	[]	[]
/src/bson-rust/src/tests/modules/bson.rs	[]	[]
/src/bson-rust/wasm-test/src/test.rs	[]	[]
/src/bson-rust/src/extjson/models.rs	[]	[]
/src/bson-rust/src/bson.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	['iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']
/src/bson-rust/src/tests/modules/document.rs	[]	[]
/src/bson-rust/src/error.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	['iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']
/src/bson-rust/src/raw/bson.rs	[]	[]
/src/bson-rust/src/de/serde.rs	[]	[]
/src/bson-rust/src/raw/serde/seeded_visitor.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	['iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']
/src/bson-rust/src/de/raw.rs	[]	[]
/src/bson-rust/src/tests/modules/macros.rs	[]	[]
/src/bson-rust/src/document.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	['iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']
/src/bson-rust/src/extjson/de.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	['iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']
/src/bson-rust/fuzz/fuzz_targets/raw_deserialize.rs	['raw_deserialize']	[]
/src/bson-rust/src/tests/binary_subtype.rs	[]	[]
/src/bson-rust/src/oid.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	['iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']
/src/bson-rust/src/raw/test.rs	[]	[]
/src/bson-rust/src/tests/spec/vector.rs	[]	[]
/src/bson-rust/src/raw.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	['iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']
/src/bson-rust/src/raw/bson_ref.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	['iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']
/src/bson-rust/src/ser/raw/value_serializer.rs	[]	[]
/src/bson-rust/src/raw/array.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	['iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']
/src/bson-rust/src/tests/modules/ser.rs	[]	[]
/src/bson-rust/src/raw/serde.rs	[]	[]
/src/bson-rust/src/raw/array_buf.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	['iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']
/src/bson-rust/src/tests/modules/lock.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	['iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']
/src/bson-rust/fuzz/generate_corpus.rs	[]	[]
/src/bson-rust/src/error/oid.rs	[]	[]
/src/bson-rust/fuzz/fuzz_targets/decode.rs	['decode']	[]
/src/bson-rust/src/ser/serde.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	['encoding', 'decode', 'raw_deserialize']
/src/bson-rust/src/error/decimal128.rs	[]	[]
/src/bson-rust/src/ser/raw/document_serializer.rs	[]	[]
/src/bson-rust/fuzz/fuzz_targets/string_handling.rs	['string_handling']	[]
/src/bson-rust/src/decimal128.rs	['raw_deserialize_utf8_lossy', 'iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']	['iterate', 'string_handling', 'type_markers', 'encoding', 'decode', 'raw_deserialize']

Directories in report

Directory
/src/bson-rust/fuzz/fuzz_targets/
/src/bson-rust/src/raw/document_buf/
/src/bson-rust/src/extjson/
/src/bson-rust/src/ser/raw/
/src/bson-rust/fuzz/
/src/bson-rust/src/ser/
/src/bson-rust/src/uuid/
/src/bson-rust/src/raw/serde/
/src/bson-rust/src/
/src/bson-rust/src/error/
/src/bson-rust/src/raw/test/
/src/bson-rust/src/tests/modules/
/src/bson-rust/serde-tests/
/src/bson-rust/src/binary/
/src/bson-rust/src/tests/
/src/bson-rust/src/tests/spec/
/src/bson-rust/src/datetime/
/src/bson-rust/src/raw/
/src/bson-rust/src/de/
/src/bson-rust/wasm-test/src/

This section shows a list of 3rd party function calls and their relative coverage information. By static analysis of the target project code, all of the 3rd party function call and their caller information, including the source file and line number that initiate the call are captured. The caller source code file and line number are shown in column 2 while column 1 is the function name of the 3rd party function call. Each occurrent of the 3rd party function call will occuply a separate row. Column 3 of each row indicate if the 3rd party call in the source file line is unreachable. Column 4 lists all fuzzers that have covered that particular system call in that specific location (source file and line)during their dynamic fuzzing.

Function in each files in report

Target sink	Callsite location	Reached by fuzzer	Covered by Fuzzers