High level conclusions

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.

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 type_markers is blocked:

The runtime code coverage of type_markers covers 28.57% 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 27.77% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer string_handling is blocked:

The runtime code coverage of string_handling covers 29.16% 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.199% of cyclomatic complexity.

Fuzzers reach 0.863% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

10 / 1158

Cyclomatic complexity statically reachable by fuzzers

22 / 1000

Runtime code coverage of functions

392 / 1158

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: 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	77	82.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	16	17.2%
All colors	93	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
33	31	Timestamp::from_le_bytes	call site: 00031	ParsedDecimal128::new
21	71	Timestamp::from_le_bytes	call site: 00071	RawDocument::new_unchecked
16	0	EP	call site: 00000	RawDocument::from_bytes
6	17	i32_from_slice	call site: 00017
1	27	i32_from_slice	call site: 00027

Runtime coverage analysis

Covered functions

115

Functions that are reachable but not covered

17

Reachable functions

24

Percentage of reachable functions covered

29.17%

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/decimal128.rs	23
src/utf8_lossy.rs	2
src/document.rs	4
src/error.rs	4
src/raw.rs	8
src/bson.rs	2
src/raw/serde/seeded_visitor.rs	6
src/raw/document.rs	1
src/raw/array.rs	1
src/oid.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	67	80.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	16	19.2%
All colors	83	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
33	31	Timestamp::from_le_bytes	call site: 00031	ParsedDecimal128::new
16	0	EP	call site: 00000	RawDocument::from_bytes
11	71	Timestamp::from_le_bytes	call site: 00071	RawDocument::new_unchecked
6	17	i32_from_slice	call site: 00017
1	27	i32_from_slice	call site: 00027

Runtime coverage analysis

Covered functions

117

Functions that are reachable but not covered

13

Reachable functions

18

Percentage of reachable functions covered

27.78%

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/decimal128.rs	23
src/utf8_lossy.rs	2
src/document.rs	4
src/error.rs	4
src/raw.rs	8
src/bson.rs	2
src/raw/serde/seeded_visitor.rs	6
src/raw/document.rs	1

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	71	81.6%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	16	18.3%
All colors	87	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
33	31	Timestamp::from_le_bytes	call site: 00031	ParsedDecimal128::new
16	0	EP	call site: 00000	RawDocument::from_bytes
15	71	Timestamp::from_le_bytes	call site: 00071	RawDocument::new_unchecked
6	17	i32_from_slice	call site: 00017
1	27	i32_from_slice	call site: 00027

Runtime coverage analysis

Covered functions

115

Functions that are reachable but not covered

15

Reachable functions

21

Percentage of reachable functions covered

28.57%

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/decimal128.rs	23
src/utf8_lossy.rs	2
src/document.rs	4
src/error.rs	4
src/raw.rs	8
src/bson.rs	2
src/raw/serde/seeded_visitor.rs	6
src/raw/document.rs	1
src/raw/array.rs	1

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	81	71.6%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	32	28.3%
All colors	113	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
26	71	Timestamp::from_le_bytes	call site: 00071	compare_docs
18	31	Timestamp::from_le_bytes	call site: 00031	ParsedDecimal128::new
14	50	Document::len	call site: 00050
7	0	EP	call site: 00000	RawDocument::from_bytes
7	9	Document::len	call site: 00009	ElementType::from
6	17	i32_from_slice	call site: 00017
2	101	compare_docs	call site: 00101
1	27	i32_from_slice	call site: 00027

Runtime coverage analysis

Covered functions

342

Functions that are reachable but not covered

15

Reachable functions

32

Percentage of reachable functions covered

53.12%

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/decimal128.rs	23
src/utf8_lossy.rs	2
src/document.rs	4
src/error.rs	4
src/raw.rs	8
src/bson.rs	2
src/raw/serde/seeded_visitor.rs	6
src/raw/document.rs	1
src/extjson/json.rs	3
src/raw/array.rs	1

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	83	90.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	9	9.78%
All colors	92	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
44	47	Timestamp::from_le_bytes	call site: 00047	ParsedDecimal128::new
34	6	Timestamp::from_le_bytes	call site: 00006	ParsedDecimal128::new
5	0	EP	call site: 00000	Document::from_reader

Runtime coverage analysis

Covered functions

326

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/de.rs	4
src/raw.rs	9
src/bson.rs	2
src/raw/serde/seeded_visitor.rs	6
src/decimal128.rs	19
src/document.rs	9
src/error.rs	4
src/ser/raw.rs	1
src/extjson/json.rs	1
src/raw/array.rs	1

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	101	66.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	51	33.5%
All colors	152	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
41	35	Document::len	call site: 00035	Serializer::serialize_newtype_struct
17	105	SerializerHint::take	call site: 00105	ParsedDecimal128::new
15	136	Serializer::new	call site: 00136	Serializer::serialize_newtype_struct
14	90	Timestamp::from_le_bytes	call site: 00090	ElementType::from
6	77	Timestamp::from_le_bytes	call site: 00077	ParsedDecimal128::new
3	0	EP	call site: 00000	ParsedDecimal128::new
3	132	ParsedDecimal128::new	call site: 00132
2	31	ParsedDecimal128::new	call site: 00031	serialize_to_buffer

Runtime coverage analysis

Covered functions

1914

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	6
src/decimal128.rs	19
src/document.rs	6
src/uuid.rs	6
src/ser/serde.rs	19
src/utf8_lossy.rs	2
src/error.rs	5
src/de.rs	4
src/raw.rs	9
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

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	101	66.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	51	33.5%
All colors	152	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
41	35	Document::len	call site: 00035	Serializer::serialize_newtype_struct
17	105	SerializerHint::take	call site: 00105	ParsedDecimal128::new
15	136	Serializer::new	call site: 00136	Serializer::serialize_newtype_struct
14	90	Timestamp::from_le_bytes	call site: 00090	ElementType::from
6	77	Timestamp::from_le_bytes	call site: 00077	ParsedDecimal128::new
3	0	EP	call site: 00000	ParsedDecimal128::new
3	132	ParsedDecimal128::new	call site: 00132
2	31	ParsedDecimal128::new	call site: 00031	serialize_to_buffer

Runtime coverage analysis

Covered functions

1982

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_utf8_lossy.rs	3
src/ser.rs	6
src/decimal128.rs	19
src/document.rs	6
src/uuid.rs	6
src/ser/serde.rs	19
src/utf8_lossy.rs	2
src/error.rs	5
src/de.rs	4
src/raw.rs	9
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

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

10 / 1158

Cyclomatic complexity statically reachable by fuzzers

22 / 1000

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/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', 'i32_from_slice']

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', 'i32_from_slice']

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', 'i32_from_slice']

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', 'i32_from_slice', 'compare_docs']

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=['Timestamp::from_le_bytes']

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

fuzz/fuzz_targets/raw_deserialize_utf8_lossy.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=['Document::len', 'SerializerHint::take', 'Serializer::new', 'Timestamp::from_le_bytes', '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	122	22	18.03%
bson::de::serde::BsonVisitor as serde::de::Visitor::visit_map::bson::de::raw::BinaryAccess	122	18	14.75%
bson::de::serde::BsonVisitor as serde::de::Visitor::visit_map::bson::de::raw::RawBsonAccess	122	41	33.60%
bson::de::serde::BsonVisitor as serde::de::Visitor::visit_map::bson::de::raw::DateTimeAccess	122	25	20.49%
bson::de::serde::BsonVisitor as serde::de::Visitor::visit_map::bson::de::raw::ObjectIdAccess	122	16	13.11%
bson::de::serde::BsonVisitor as serde::de::Visitor::visit_map::bson::de::raw::DbPointerAccess	122	23	18.85%
bson::de::serde::BsonVisitor as serde::de::Visitor::visit_map::bson::de::raw::TimestampAccess	122	23	18.85%
bson::de::serde::BsonVisitor as serde::de::Visitor::visit_map::bson::de::raw::CodeWithScopeAccess	122	24	19.67%
bson::de::serde::BsonVisitor as serde::de::Visitor::visit_map::bson::de::raw::Decimal128Access	122	30	24.59%
&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::serde_bytes::bytes::Bytes	88	11	12.5%
&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::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::&bson::raw::cstr::CStr	88	12	13.63%
&mut bson::ser::raw::value_serializer::ValueSerializer as serde::ser::SerializeStruct::serialize_field::&str	88	9	10.22%
&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%
bson::de::raw::RawDeserializer as serde::de::Deserializer::deserialize_newtype_struct::bson::utf8_lossy::Utf8Lossy_ as serde::de::Deserialize::deserialize::Vbson::document::Document	42	19	45.23%
bson::de::serde::BsonVisitor as serde::de::Visitor::visit_map::bson::de::serde::MapDeserializer	122	21	17.21%
bson::de::serde::Deserializer::deserialize_next::serde::de::impls::StringVisitor	39	11	28.20%
bson::de::serde::Deserializer::deserialize_next::serde::__private::de::content::ContentVisitor	39	11	28.20%
bson::de::serde::Deserializer::deserialize_next::bson::extjson::models::ObjectId as serde::de::Deserialize::deserialize::__FieldVisitor	39	11	28.20%
bson::de::serde::Deserializer::deserialize_next::bson::extjson::models::RegexBody as serde::de::Deserialize::deserialize::__FieldVisitor	39	11	28.20%
bson::de::serde::Deserializer::deserialize_next::bson::extjson::models::BinaryBody as serde::de::Deserialize::deserialize::__FieldVisitor	39	11	28.20%
bson::de::serde::Deserializer::deserialize_next::bson::extjson::models::TimestampBody as serde::de::Deserialize::deserialize::__FieldVisitor	39	11	28.20%
bson::de::serde::Deserializer::deserialize_next::bson::extjson::models::DbPointerBody as serde::de::Deserialize::deserialize::__FieldVisitor	39	11	28.20%

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

Directories in report

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

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