High level conclusions

Fuzzer end_session_rsp is blocked:

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

Fuzzer encapsulated_request_certificate_req is blocked:

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

Fuzzer finish_req is blocked:

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

Fuzzer key_update_rsp is blocked:

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

Fuzzer measurement_rsp is blocked:

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

Fuzzer vendor_req is blocked:

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

Fuzzer certificate_rsp is blocked:

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

Fuzzer digest_rsp is blocked:

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

Fuzzer pskexchange_rsp is blocked:

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

Fuzzer psk_exchange_req is blocked:

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

Fuzzer psk_finish_req is blocked:

The runtime code coverage of psk_finish_req covers 5.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 keyexchange_rsp is blocked:

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

Fuzzer heartbeat_req is blocked:

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

Fuzzer capability_rsp is blocked:

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

Fuzzer algorithm_rsp is blocked:

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

Fuzzer algorithm_req is blocked:

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

Fuzzer end_session_req is blocked:

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

Fuzzer key_exchange_req is blocked:

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

Fuzzer psk_finish_rsp is blocked:

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

Fuzzer finish_rsp is blocked:

The runtime code coverage of finish_rsp covers 4.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 digest_req is blocked:

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

Fuzzer encapsulated_request_req is blocked:

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

Fuzzer version_req is blocked:

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

Fuzzer deliver_encapsulated_response_certificate_rsp is blocked:

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

Fuzzer key_update_req is blocked:

The runtime code coverage of key_update_req covers 10.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 version_rsp is blocked:

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

Fuzzer deliver_encapsulated_response_rsp is blocked:

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

Fuzzer capability_req is blocked:

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

Fuzzer certificate_req is blocked:

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

Fuzzer vendor_rsp is blocked:

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

Fuzzer measurement_req is blocked:

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

Fuzzer encapsulated_request_digest_req is blocked:

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

Fuzzer challenge_req is blocked:

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

Fuzzer challenge_rsp is blocked:

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

Fuzzer get_encapsulated_request_rsp is blocked:

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

Fuzzer deliver_encapsulated_response_digest_rsp is blocked:

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

Fuzzer heartbeat_rsp is blocked:

The runtime code coverage of heartbeat_rsp covers 5.454% 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 4.268% of cyclomatic complexity.

Fuzzers reach 3.022% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

84 / 2779

Cyclomatic complexity statically reachable by fuzzers

279 / 6536

Runtime code coverage of functions

163 / 2779

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

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	262	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	262	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
261	0	EP	call site: 00000	fuzz_handle_spdm_heartbeat

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

52

Reachable functions

55

Percentage of reachable functions covered

5.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.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
spdmlib/fuzz/fuzz_targets/heartbeat_rsp.rs	4
fuzz-target/responder/heartbeat_rsp/src/main.rs	16
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	2
spdmlib/src/crypto/bytes_mut_scrubbed.rs	7
test/spdmlib-test/src/common/util.rs	19
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	10
spdmlib/src/common/session.rs	6
test/spdmlib-test/src/responder_tests/heartbeat_rsp.rs	18
test/spdm-emu/src/async_runtime.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2

Fuzzer: deliver_encapsulated_response_digest_rsp

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	219	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	219	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
218	0	EP	call site: 00000	fuzz_handle_encap_response_digest

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

36

Reachable functions

39

Percentage of reachable functions covered

7.69%

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
spdmlib/fuzz/fuzz_targets/deliver_encapsulated_response_digest_rsp.rs	4
fuzz-target/responder/deliver_encapsulated_response_digest_rsp/src/main.rs	11
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	2
spdmlib/src/crypto/bytes_mut_scrubbed.rs	6
test/spdmlib-test/src/common/util.rs	19
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	7
test/spdmlib-test/src/responder_tests/encap_get_digest.rs	13

Fuzzer: get_encapsulated_request_rsp

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	529	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	529	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
528	0	EP	call site: 00000	SpdmSession::decode_spdm_secured_message

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

39

Reachable functions

42

Percentage of reachable functions covered

7.14%

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
spdmlib/fuzz/fuzz_targets/get_encapsulated_request_rsp.rs	4
fuzz-target/responder/get_encapsulated_request_rsp/src/main.rs	14
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	3
spdmlib/src/crypto/bytes_mut_scrubbed.rs	8
test/spdmlib-test/src/common/util.rs	38
tdisp/src/pci_tdisp.rs	3
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	12
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	10
test/spdmlib-test/src/responder_tests/encap_rsp.rs	18
test/spdmlib-test/src/requester_tests/encap_req.rs	13
spdmlib/src/common/session.rs	20
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
test/spdm-emu/src/tcp_transport.rs	4
external/ring/src/testutil.rs	8
test/spdmlib-test/src/responder_tests/context.rs	15
test/spdmlib-test/src/common/device_io.rs	6
test/spdm-emu/src/async_runtime.rs	3
spdmlib/src/common/mod.rs	13
test/spdmlib-test/src/common/crypto_callback.rs	3
spdmlib/src/message/heartbeat.rs	2

Fuzzer: challenge_rsp

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	1353	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	1353	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
1352	0	EP	call site: 00000	SpdmMessage::spdm_read

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

48

Reachable functions

51

Percentage of reachable functions covered

5.88%

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
spdmlib/fuzz/fuzz_targets/challenge_rsp.rs	4
fuzz-target/responder/challenge_rsp/src/main.rs	15
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	3
spdmlib/src/crypto/bytes_mut_scrubbed.rs	9
test/spdmlib-test/src/common/util.rs	42
tdisp/src/pci_tdisp.rs	3
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	27
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	14
test/spdmlib-test/src/common/crypto_callback.rs	3
spdmlib/src/crypto/mod.rs	3
external/ring/src/testutil.rs	8
test/spdmlib-test/src/responder_tests/context.rs	15
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
spdmlib/src/common/session.rs	6
test/spdm-emu/src/async_runtime.rs	3
test/spdmlib-test/src/responder_tests/challenge_rsp.rs	26
spdmlib/src/message/heartbeat.rs	75
spdmlib/src/message/mod.rs	60
spdmlib/src/message/vendor.rs	2
external/ring/src/bits.rs	1
spdmlib/src/protocol/algo.rs	3
spdmlib/src/common/mod.rs	6
spdmlib/src/responder/context.rs	18
spdmlib/src/responder/error_rsp.rs	4
external/ring/src/rand.rs	3
spdmlib/src/common/spdm_codec.rs	6

Fuzzer: challenge_req

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	516	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	516	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
515	0	EP	call site: 00000	fuzz_send_receive_spdm_challenge

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

50

Reachable functions

53

Percentage of reachable functions covered

5.66%

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
spdmlib/fuzz/fuzz_targets/challenge_req.rs	4
fuzz-target/requester/challenge_req/src/main.rs	17
test/spdmlib-test/src/common/util.rs	42
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/crypto/bytes_mut_scrubbed.rs	8
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	15
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	3
fuzz-target/fuzzlib/src/fake_device_io.rs	2
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
spdmlib/src/common/mod.rs	1
test/spdmlib-test/src/common/crypto_callback.rs	3
spdmlib/src/crypto/mod.rs	3
external/ring/src/testutil.rs	8
test/spdmlib-test/src/responder_tests/context.rs	15
spdmlib/src/common/session.rs	6
test/spdm-emu/src/async_runtime.rs	3
test/spdmlib-test/src/requester_tests/challenge_req.rs	18

Fuzzer: encapsulated_request_digest_req

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	542	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	542	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
541	0	EP	call site: 00000	SpdmDigestsResponsePayload::spdm_read

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

63

Reachable functions

66

Percentage of reachable functions covered

4.55%

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
spdmlib/fuzz/fuzz_targets/encapsulated_request_digest_req.rs	4
fuzz-target/requester/encapsulated_request_digest_req/src/main.rs	20
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	3
spdmlib/src/crypto/bytes_mut_scrubbed.rs	8
test/spdmlib-test/src/common/util.rs	42
tdisp/src/pci_tdisp.rs	3
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	14
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	15
test/spdmlib-test/src/common/crypto_callback.rs	3
spdmlib/src/crypto/mod.rs	3
external/ring/src/testutil.rs	8
test/spdmlib-test/src/responder_tests/context.rs	15
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
spdmlib/src/common/session.rs	6
test/spdm-emu/src/async_runtime.rs	3
test/spdmlib-test/src/requester_tests/encap_digest.rs	16
spdmlib/src/message/heartbeat.rs	12
spdmlib/src/common/mod.rs	1
external/ring/src/bits.rs	1

Fuzzer: measurement_req

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	631	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	631	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
630	0	EP	call site: 00000	SpdmKeySchedule::derive_master_secret

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

74

Reachable functions

77

Percentage of reachable functions covered

3.9%

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
spdmlib/fuzz/fuzz_targets/measurement_req.rs	4
fuzz-target/requester/measurement_req/src/main.rs	26
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	3
spdmlib/src/crypto/bytes_mut_scrubbed.rs	13
test/spdmlib-test/src/common/util.rs	42
tdisp/src/pci_tdisp.rs	3
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	15
fuzz-target/fuzzlib/src/fake_device_io.rs	2
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
test/spdmlib-test/src/common/crypto_callback.rs	4
spdmlib/src/crypto/mod.rs	5
external/ring/src/testutil.rs	8
test/spdmlib-test/src/responder_tests/context.rs	15
spdmlib/src/common/session.rs	9
test/spdm-emu/src/async_runtime.rs	3
spdmlib/src/common/mod.rs	5
test/spdmlib-test/src/requester_tests/get_measurements_req.rs	22
spdmlib/src/common/key_schedule.rs	21
spdmlib/src/protocol/algo.rs	4

Fuzzer: vendor_rsp

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	222	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	222	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
221	0	EP	call site: 00000	fuzz_handle_spdm_vendor_defined_request

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

41

Reachable functions

44

Percentage of reachable functions covered

6.82%

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
spdmlib/fuzz/fuzz_targets/vendor_rsp.rs	4
fuzz-target/responder/vendor_rsp/src/main.rs	15
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	2
spdmlib/src/crypto/bytes_mut_scrubbed.rs	6
test/spdmlib-test/src/common/util.rs	19
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	7
spdmlib/src/message/vendor.rs	2
test/spdmlib-test/src/responder_tests/vendor_rsp.rs	13
spdmlib/src/responder/vendor_rsp.rs	1

Fuzzer: certificate_req

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	537	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	537	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
536	0	EP	call site: 00000	SpdmCertificateResponsePayload::spdm_read

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

64

Reachable functions

65

Percentage of reachable functions covered

1.54%

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
spdmlib/fuzz/fuzz_targets/certificate_req.rs	4
fuzz-target/requester/encapsulated_request_certificate_req/src/main.rs	19
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	3
spdmlib/src/crypto/bytes_mut_scrubbed.rs	8
test/spdmlib-test/src/common/util.rs	42
tdisp/src/pci_tdisp.rs	3
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	12
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	15
test/spdmlib-test/src/common/crypto_callback.rs	3
spdmlib/src/crypto/mod.rs	3
external/ring/src/testutil.rs	8
test/spdmlib-test/src/responder_tests/context.rs	15
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
spdmlib/src/common/session.rs	6
test/spdm-emu/src/async_runtime.rs	3
test/spdmlib-test/src/requester_tests/encap_certificate.rs	16
spdmlib/src/message/heartbeat.rs	7

Fuzzer: capability_req

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	260	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	260	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
259	0	EP	call site: 00000	fuzz_send_receive_spdm_capability

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

36

Reachable functions

39

Percentage of reachable functions covered

7.69%

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
spdmlib/fuzz/fuzz_targets/capability_req.rs	4
fuzz-target/requester/capability_req/src/main.rs	10
test/spdmlib-test/src/common/util.rs	22
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/crypto/bytes_mut_scrubbed.rs	8
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	8
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	2
fuzz-target/fuzzlib/src/fake_device_io.rs	2
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
test/spdmlib-test/src/requester_tests/get_capabilities_req.rs	15
spdmlib/src/common/mod.rs	1
test/spdm-emu/src/async_runtime.rs	3

Fuzzer: deliver_encapsulated_response_rsp

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	235	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	235	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
234	0	EP	call site: 00000	fuzz_handle_deliver_encapsulated_reponse

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

40

Reachable functions

43

Percentage of reachable functions covered

6.98%

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
spdmlib/fuzz/fuzz_targets/deliver_encapsulated_response_rsp.rs	4
fuzz-target/responder/deliver_encapsulated_response_rsp/src/main.rs	15
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	2
spdmlib/src/crypto/bytes_mut_scrubbed.rs	6
test/spdmlib-test/src/common/util.rs	19
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	7

Fuzzer: version_rsp

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	1303	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	1303	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
1302	0	EP	call site: 00000	SpdmMessage::spdm_read

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

43

Reachable functions

46

Percentage of reachable functions covered

6.52%

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
spdmlib/fuzz/fuzz_targets/version_rsp.rs	4
fuzz-target/responder/version_rsp/src/main.rs	14
test/spdmlib-test/src/common/util.rs	38
tdisp/src/pci_tdisp.rs	3
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	27
codec/src/codec.rs	7
spdmlib/src/crypto/bytes_mut_scrubbed.rs	9
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	10
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	3
test/spdmlib-test/src/responder_tests/version_rsp.rs	18
external/ring/src/testutil.rs	8
test/spdmlib-test/src/responder_tests/context.rs	15
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
spdmlib/src/common/session.rs	6
test/spdm-emu/src/async_runtime.rs	3
spdmlib/src/message/heartbeat.rs	75
spdmlib/src/message/mod.rs	60
spdmlib/src/message/vendor.rs	2
external/ring/src/bits.rs	1
spdmlib/src/protocol/algo.rs	3
spdmlib/src/common/mod.rs	6
spdmlib/src/responder/context.rs	18
spdmlib/src/responder/error_rsp.rs	4
external/ring/src/rand.rs	3
spdmlib/src/common/spdm_codec.rs	6
test/spdm-emu/src/tcp_transport.rs	4

Fuzzer: key_update_req

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	339	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	339	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
338	0	EP	call site: 00000	ResponderRunner::run

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

9

Reachable functions

10

Percentage of reachable functions covered

10.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
spdmlib/fuzz/fuzz_targets/key_update_req.rs	4
fuzz-target/requester/key_update_req/src/main.rs	6
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	3
spdmlib/src/crypto/bytes_mut_scrubbed.rs	8
test/spdmlib-test/src/common/util.rs	42
test/spdmlib-test/src/common/crypto_callback.rs	3
spdmlib/src/crypto/mod.rs	3
external/ring/src/testutil.rs	8
test/spdm-emu/src/spdm_emu.rs	7
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	14
test/spdmlib-test/src/responder_tests/context.rs	15
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
spdmlib/src/common/session.rs	6
test/spdm-emu/src/async_runtime.rs	3

Fuzzer: deliver_encapsulated_response_certificate_rsp

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	249	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	249	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
248	0	EP	call site: 00000	fuzz_handle_encap_response_certificate

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

39

Reachable functions

42

Percentage of reachable functions covered

7.14%

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
spdmlib/fuzz/fuzz_targets/deliver_encapsulated_response_certificate_rsp.rs	4
fuzz-target/responder/deliver_encapsulated_response_certificate_rsp/src/main.rs	17
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	2
spdmlib/src/crypto/bytes_mut_scrubbed.rs	7
test/spdmlib-test/src/common/util.rs	19
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	7
test/spdmlib-test/src/responder_tests/encap_get_certificate.rs	16

Fuzzer: version_req

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	265	99.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	1	0.37%
lawngreen	50+	1	0.37%
All colors	267	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
192	0	EP	call site: 00000	fuzz_send_receive_spdm_version
73	193	Self::send_receive_spdm_version	call site: 00193	SpdmSocketHeader::encode

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

14

Reachable functions

16

Percentage of reachable functions covered

12.5%

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
spdmlib/fuzz/fuzz_targets/version_req.rs	4
fuzz-target/requester/version_req/src/main.rs	10
test/spdmlib-test/src/common/util.rs	22
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/crypto/bytes_mut_scrubbed.rs	8
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	8
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	2
fuzz-target/fuzzlib/src/fake_device_io.rs	2
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
test/spdmlib-test/src/requester_tests/get_version_req.rs	13
test/spdm-emu/src/async_runtime.rs	3

Fuzzer: encapsulated_request_req

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	341	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	341	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
340	0	EP	call site: 00000	fuzz_session_based_mutual_authenticate

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

55

Reachable functions

58

Percentage of reachable functions covered

5.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.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
spdmlib/fuzz/fuzz_targets/encapsulated_request_req.rs	4
fuzz-target/requester/encapsulated_request_req/src/main.rs	19
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	2
spdmlib/src/crypto/bytes_mut_scrubbed.rs	8
test/spdmlib-test/src/common/util.rs	22
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	10
fuzz-target/fuzzlib/src/fake_device_io.rs	2
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
spdmlib/src/common/session.rs	6

Fuzzer: digest_req

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	542	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	542	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
541	0	EP	call site: 00000	SpdmDigestsResponsePayload::spdm_read

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

65

Reachable functions

66

Percentage of reachable functions covered

1.52%

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
spdmlib/fuzz/fuzz_targets/digest_req.rs	4
fuzz-target/requester/encapsulated_request_digest_req/src/main.rs	20
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	3
spdmlib/src/crypto/bytes_mut_scrubbed.rs	8
test/spdmlib-test/src/common/util.rs	42
tdisp/src/pci_tdisp.rs	3
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	14
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	15
test/spdmlib-test/src/common/crypto_callback.rs	3
spdmlib/src/crypto/mod.rs	3
external/ring/src/testutil.rs	8
test/spdmlib-test/src/responder_tests/context.rs	15
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
spdmlib/src/common/session.rs	6
test/spdm-emu/src/async_runtime.rs	3
test/spdmlib-test/src/requester_tests/encap_digest.rs	16
spdmlib/src/message/heartbeat.rs	12
spdmlib/src/common/mod.rs	1
external/ring/src/bits.rs	1

Fuzzer: finish_rsp

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	648	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	648	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
647	0	EP	call site: 00000	SpdmKeySchedule::derive_master_secret

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

72

Reachable functions

75

Percentage of reachable functions covered

4.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
spdmlib/fuzz/fuzz_targets/finish_rsp.rs	4
fuzz-target/responder/finish_rsp/src/main.rs	29
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	3
spdmlib/src/crypto/bytes_mut_scrubbed.rs	13
test/spdmlib-test/src/common/util.rs	42
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	14
test/spdmlib-test/src/common/crypto_callback.rs	4
spdmlib/src/crypto/mod.rs	5
external/ring/src/testutil.rs	8
test/spdmlib-test/src/responder_tests/context.rs	15
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
spdmlib/src/common/session.rs	9
test/spdm-emu/src/async_runtime.rs	3
spdmlib/src/common/key_schedule.rs	21
spdmlib/src/protocol/algo.rs	4
test/spdmlib-test/src/responder_tests/finish_rsp.rs	21
spdmlib/src/common/mod.rs	4

Fuzzer: psk_finish_rsp

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	485	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	485	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
484	0	EP	call site: 00000	ResponderRunner::run

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

59

Reachable functions

62

Percentage of reachable functions covered

4.84%

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
spdmlib/fuzz/fuzz_targets/psk_finish_rsp.rs	4
fuzz-target/responder/psk_finish_rsp/src/main.rs	24
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	3
spdmlib/src/crypto/bytes_mut_scrubbed.rs	13
test/spdmlib-test/src/common/util.rs	38
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	10
spdmlib/src/common/session.rs	6
spdmlib/src/crypto/mod.rs	5
external/ring/src/testutil.rs	8
test/spdmlib-test/src/responder_tests/context.rs	15
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
test/spdm-emu/src/async_runtime.rs	3
test/spdmlib-test/src/responder_tests/psk_finish_rsp.rs	22
spdmlib/src/message/heartbeat.rs	3
spdmlib/src/common/mod.rs	4

Fuzzer: key_exchange_req

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	531	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	531	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
530	0	EP	call site: 00000	fuzz_send_receive_spdm_key_exchange

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

51

Reachable functions

54

Percentage of reachable functions covered

5.56%

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
spdmlib/fuzz/fuzz_targets/key_exchange_req.rs	4
fuzz-target/requester/key_exchange_req/src/main.rs	18
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	3
spdmlib/src/crypto/bytes_mut_scrubbed.rs	8
test/spdmlib-test/src/common/util.rs	42
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	15
fuzz-target/fuzzlib/src/fake_device_io.rs	2
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
test/spdmlib-test/src/common/crypto_callback.rs	3
spdmlib/src/crypto/mod.rs	3
external/ring/src/testutil.rs	8
test/spdmlib-test/src/responder_tests/context.rs	15
spdmlib/src/common/session.rs	6
test/spdm-emu/src/async_runtime.rs	3
spdmlib/src/common/mod.rs	1
test/spdmlib-test/src/requester_tests/key_exchange_req.rs	17

Fuzzer: fuzz_x509v3

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	42	16.0%
gold	[1:9]	1	0.38%
yellow	[10:29]	6	2.29%
greenyellow	[30:49]	9	3.44%
lawngreen	50+	203	77.7%
All colors	261	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
5	54	object_identifiers_are_same	call site: 00054
2	2	check_cert_chain_format	call site: 00002
2	162	check_cert_chain_format	call site: 00162	check_leaf_certificate
2	237	check_leaf_certificate	call site: 00237	check_leaf_certificate
1	0	EP	call site: 00000	check_cert_chain_format
1	8	check_tag_is_sequence	call site: 00008
1	26	check_tbs_certificate	call site: 00026
1	36	check_and_skip_common_tag	call site: 00036
1	46	object_identifiers_are_same	call site: 00046
1	49	object_identifiers_are_same	call site: 00049	SocketIoTransport::new
1	52	object_identifiers_are_same	call site: 00052	SocketIoTransport::new
1	64	get_oid_by_base_asym_algo	call site: 00064

Runtime coverage analysis

Covered functions

40

Functions that are reachable but not covered

14

Reachable functions

43

Percentage of reachable functions covered

67.44%

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
spdmlib/fuzz/fuzz_targets/fuzz_x509v3.rs	4
spdmlib/src/crypto/x509v3.rs	34
spdmlib/src/crypto/bytes_mut_scrubbed.rs	3
tdisp/src/pci_tdisp.rs	1

Fuzzer: end_session_req

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	347	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	347	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
346	0	EP	call site: 00000	fuzz_send_receive_spdm_end_session

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

53

Reachable functions

56

Percentage of reachable functions covered

5.36%

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
spdmlib/fuzz/fuzz_targets/end_session_req.rs	4
fuzz-target/requester/end_session_req/src/main.rs	17
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	2
spdmlib/src/crypto/bytes_mut_scrubbed.rs	8
test/spdmlib-test/src/common/util.rs	22
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	11
fuzz-target/fuzzlib/src/fake_device_io.rs	2
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
spdmlib/src/common/session.rs	6
test/spdmlib-test/src/requester_tests/end_session_req.rs	20
test/spdm-emu/src/async_runtime.rs	3

Fuzzer: algorithm_req

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	259	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	259	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
258	0	EP	call site: 00000	fuzz_send_receive_spdm_algorithm

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

37

Reachable functions

40

Percentage of reachable functions covered

7.5%

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
spdmlib/fuzz/fuzz_targets/algorithm_req.rs	4
fuzz-target/requester/algorithm_req/src/main.rs	11
test/spdmlib-test/src/common/util.rs	22
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/crypto/bytes_mut_scrubbed.rs	8
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	8
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	2
fuzz-target/fuzzlib/src/fake_device_io.rs	2
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
test/spdmlib-test/src/requester_tests/negotiate_algorithms_req.rs	14
test/spdm-emu/src/async_runtime.rs	3

Fuzzer: algorithm_rsp

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	1294	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	1294	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
1293	0	EP	call site: 00000	SpdmMessage::spdm_read

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

37

Reachable functions

40

Percentage of reachable functions covered

7.5%

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
spdmlib/fuzz/fuzz_targets/algorithm_rsp.rs	4
fuzz-target/responder/algorithm_rsp/src/main.rs	11
test/spdmlib-test/src/common/util.rs	38
tdisp/src/pci_tdisp.rs	3
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	27
codec/src/codec.rs	7
spdmlib/src/crypto/bytes_mut_scrubbed.rs	9
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	10
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	3
test/spdmlib-test/src/responder_tests/algorithm_rsp.rs	30
external/ring/src/testutil.rs	8
test/spdmlib-test/src/responder_tests/context.rs	15
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
spdmlib/src/common/session.rs	6
test/spdm-emu/src/async_runtime.rs	3
spdmlib/src/message/heartbeat.rs	75
external/ring/src/bits.rs	1
spdmlib/src/message/mod.rs	60
spdmlib/src/message/vendor.rs	2
spdmlib/src/protocol/algo.rs	3
spdmlib/src/common/mod.rs	6
spdmlib/src/responder/context.rs	18
spdmlib/src/responder/error_rsp.rs	4
external/ring/src/rand.rs	3
spdmlib/src/common/spdm_codec.rs	6

Fuzzer: capability_rsp

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	1287	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	1287	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
1286	0	EP	call site: 00000	SpdmMessage::spdm_read

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

37

Reachable functions

40

Percentage of reachable functions covered

7.5%

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
spdmlib/fuzz/fuzz_targets/capability_rsp.rs	4
fuzz-target/responder/capability_rsp/src/main.rs	11
test/spdmlib-test/src/common/util.rs	38
tdisp/src/pci_tdisp.rs	3
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	27
codec/src/codec.rs	7
spdmlib/src/crypto/bytes_mut_scrubbed.rs	9
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	10
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	3
test/spdmlib-test/src/responder_tests/capability_rsp.rs	23
external/ring/src/testutil.rs	8
test/spdmlib-test/src/responder_tests/context.rs	15
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
spdmlib/src/common/session.rs	6
test/spdm-emu/src/async_runtime.rs	3
spdmlib/src/message/heartbeat.rs	75
external/ring/src/bits.rs	1
spdmlib/src/message/mod.rs	60
spdmlib/src/message/vendor.rs	2
spdmlib/src/protocol/algo.rs	3
spdmlib/src/common/mod.rs	6
spdmlib/src/responder/context.rs	18
spdmlib/src/responder/error_rsp.rs	4
external/ring/src/rand.rs	3
spdmlib/src/common/spdm_codec.rs	6

Fuzzer: heartbeat_req

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	306	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	306	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
305	0	EP	call site: 00000	fuzz_send_receive_spdm_heartbeat

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

53

Reachable functions

56

Percentage of reachable functions covered

5.36%

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
spdmlib/fuzz/fuzz_targets/heartbeat_req.rs	4
fuzz-target/requester/heartbeat_req/src/main.rs	17
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	2
spdmlib/src/crypto/bytes_mut_scrubbed.rs	8
test/spdmlib-test/src/common/util.rs	22
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	11
fuzz-target/fuzzlib/src/fake_device_io.rs	2
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
spdmlib/src/common/session.rs	6
test/spdmlib-test/src/requester_tests/heartbeat_req.rs	20
test/spdm-emu/src/async_runtime.rs	3

Fuzzer: keyexchange_rsp

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	624	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	624	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
623	0	EP	call site: 00000	ResponderContext::handle_spdm_chunk_get

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

48

Reachable functions

51

Percentage of reachable functions covered

5.88%

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
spdmlib/fuzz/fuzz_targets/keyexchange_rsp.rs	4
fuzz-target/responder/keyexchange_rsp/src/main.rs	15
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	3
spdmlib/src/crypto/bytes_mut_scrubbed.rs	9
test/spdmlib-test/src/common/util.rs	42
tdisp/src/pci_tdisp.rs	6
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	12
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	15
test/spdmlib-test/src/common/crypto_callback.rs	6
spdmlib/src/crypto/mod.rs	3
external/ring/src/testutil.rs	8
test/spdmlib-test/src/responder_tests/context.rs	15
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
spdmlib/src/common/session.rs	6
test/spdm-emu/src/async_runtime.rs	3
spdmlib/src/common/mod.rs	1
test/spdmlib-test/src/responder_tests/key_exchange_rsp.rs	27
external/ring/src/hmac.rs	3
external/ring/src/cpu.rs	1
external/ring/src/polyfill/once_cell/race.rs	5
spdmlib/src/message/heartbeat.rs	11
spdmlib/src/message/mod_test.common.inc.rs	5
spdmlib/src/responder/context.rs	18
spdmlib/src/responder/error_rsp.rs	4
external/ring/src/rand.rs	3
external/ring/src/agreement.rs	9
spdmlib/src/protocol/algo.rs	1
spdmlib/src/common/opaque.rs	3

Fuzzer: psk_finish_req

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	600	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	600	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
599	0	EP	call site: 00000	SpdmKeySchedule::derive_aead_key_iv

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

57

Reachable functions

60

Percentage of reachable functions covered

5.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
spdmlib/fuzz/fuzz_targets/psk_finish_req.rs	4
fuzz-target/requester/psk_finish_req/src/main.rs	22
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	3
spdmlib/src/crypto/bytes_mut_scrubbed.rs	13
test/spdmlib-test/src/common/util.rs	38
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	11
fuzz-target/fuzzlib/src/fake_device_io.rs	2
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
spdmlib/src/common/session.rs	14
spdmlib/src/crypto/mod.rs	5
external/ring/src/testutil.rs	8
test/spdmlib-test/src/responder_tests/context.rs	15
test/spdm-emu/src/async_runtime.rs	3
test/spdmlib-test/src/requester_tests/psk_finish_req.rs	25
spdmlib/src/common/key_schedule.rs	24
test/spdmlib-test/src/common/crypto_callback.rs	3
spdmlib/src/protocol/algo.rs	4
spdmlib/src/secret/mod.rs	3

Fuzzer: psk_exchange_req

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	307	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	307	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
306	0	EP	call site: 00000	fuzz_send_receive_spdm_psk_exchange

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

40

Reachable functions

43

Percentage of reachable functions covered

6.98%

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
spdmlib/fuzz/fuzz_targets/psk_exchange_req.rs	4
fuzz-target/requester/psk_exchange_req/src/main.rs	14
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	2
spdmlib/src/crypto/bytes_mut_scrubbed.rs	8
test/spdmlib-test/src/common/util.rs	22
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	8
fuzz-target/fuzzlib/src/fake_device_io.rs	2
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
test/spdmlib-test/src/requester_tests/psk_exchange_req.rs	16
test/spdm-emu/src/async_runtime.rs	3

Fuzzer: pskexchange_rsp

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	310	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	310	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
309	0	EP	call site: 00000	fuzz_handle_spdm_psk_exchange

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

53

Reachable functions

56

Percentage of reachable functions covered

5.36%

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
spdmlib/fuzz/fuzz_targets/pskexchange_rsp.rs	4
fuzz-target/responder/pskexchange_rsp/src/main.rs	17
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	2
spdmlib/src/crypto/bytes_mut_scrubbed.rs	7
test/spdmlib-test/src/common/util.rs	19
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	10
spdmlib/src/common/mod.rs	1
test/spdmlib-test/src/responder_tests/psk_exchange_rsp.rs	14
spdmlib/src/common/opaque.rs	3
spdmlib/src/message/heartbeat.rs	3
test/spdm-emu/src/async_runtime.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
spdmlib/src/common/session.rs	6

Fuzzer: digest_rsp

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	219	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	219	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
218	0	EP	call site: 00000	fuzz_handle_encap_response_digest

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

38

Reachable functions

39

Percentage of reachable functions covered

2.56%

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
spdmlib/fuzz/fuzz_targets/digest_rsp.rs	4
fuzz-target/responder/deliver_encapsulated_response_digest_rsp/src/main.rs	11
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	2
spdmlib/src/crypto/bytes_mut_scrubbed.rs	6
test/spdmlib-test/src/common/util.rs	19
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	7
test/spdmlib-test/src/responder_tests/encap_get_digest.rs	13

Fuzzer: certificate_rsp

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	1340	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	1340	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
1339	0	EP	call site: 00000	SpdmMessage::spdm_read

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

62

Reachable functions

65

Percentage of reachable functions covered

4.62%

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
spdmlib/fuzz/fuzz_targets/certificate_rsp.rs	4
fuzz-target/responder/certificate_rsp/src/main.rs	19
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	3
spdmlib/src/crypto/bytes_mut_scrubbed.rs	9
test/spdmlib-test/src/common/util.rs	42
tdisp/src/pci_tdisp.rs	3
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	27
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	14
test/spdmlib-test/src/common/crypto_callback.rs	3
spdmlib/src/crypto/mod.rs	3
external/ring/src/testutil.rs	8
test/spdmlib-test/src/responder_tests/context.rs	15
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
spdmlib/src/common/session.rs	6
test/spdm-emu/src/async_runtime.rs	3
test/spdmlib-test/src/responder_tests/certificate_rsp.rs	22
spdmlib/src/message/heartbeat.rs	75
spdmlib/src/message/mod.rs	60
spdmlib/src/message/vendor.rs	2
external/ring/src/bits.rs	1
spdmlib/src/protocol/algo.rs	3
spdmlib/src/common/mod.rs	6
spdmlib/src/responder/context.rs	18
spdmlib/src/responder/error_rsp.rs	4
external/ring/src/rand.rs	3
spdmlib/src/common/spdm_codec.rs	6

Fuzzer: vendor_req

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	259	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	259	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
258	0	EP	call site: 00000	fuzz_send_spdm_vendor_defined_request

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

37

Reachable functions

40

Percentage of reachable functions covered

7.5%

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
spdmlib/fuzz/fuzz_targets/vendor_req.rs	4
fuzz-target/requester/vendor_req/src/main.rs	11
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	2
spdmlib/src/crypto/bytes_mut_scrubbed.rs	8
test/spdmlib-test/src/common/util.rs	22
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	8
fuzz-target/fuzzlib/src/fake_device_io.rs	2
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
test/spdmlib-test/src/requester_tests/vendor_req.rs	14
test/spdm-emu/src/async_runtime.rs	3

Fuzzer: measurement_rsp

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	1347	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	1347	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
1346	0	EP	call site: 00000	SpdmMessage::spdm_read

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

62

Reachable functions

65

Percentage of reachable functions covered

4.62%

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
spdmlib/fuzz/fuzz_targets/measurement_rsp.rs	4
fuzz-target/responder/measurement_rsp/src/main.rs	19
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	3
spdmlib/src/crypto/bytes_mut_scrubbed.rs	9
test/spdmlib-test/src/common/util.rs	42
tdisp/src/pci_tdisp.rs	3
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	27
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	14
test/spdmlib-test/src/common/crypto_callback.rs	3
spdmlib/src/crypto/mod.rs	3
external/ring/src/testutil.rs	8
test/spdmlib-test/src/responder_tests/context.rs	15
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
spdmlib/src/common/session.rs	6
test/spdm-emu/src/async_runtime.rs	3
test/spdmlib-test/src/responder_tests/measurement_rsp.rs	25
spdmlib/src/message/heartbeat.rs	75
external/ring/src/bits.rs	1
spdmlib/src/message/mod.rs	60
spdmlib/src/message/vendor.rs	2
spdmlib/src/protocol/algo.rs	3
spdmlib/src/common/mod.rs	6
spdmlib/src/responder/context.rs	18
spdmlib/src/responder/error_rsp.rs	4
external/ring/src/rand.rs	3
spdmlib/src/common/spdm_codec.rs	6

Fuzzer: key_update_rsp

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	625	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	625	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
624	0	EP	call site: 00000	SpdmKeySchedule::derive_aead_key_iv

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

52

Reachable functions

55

Percentage of reachable functions covered

5.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.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
spdmlib/fuzz/fuzz_targets/key_update_rsp.rs	4
fuzz-target/responder/key_update_rsp/src/main.rs	16
test/spdmlib-test/src/common/util.rs	38
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/crypto/bytes_mut_scrubbed.rs	13
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	10
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	3
spdmlib/src/common/session.rs	20
test/spdmlib-test/src/responder_tests/key_update_rsp.rs	23
spdmlib/src/common/key_schedule.rs	35
test/spdmlib-test/src/common/crypto_callback.rs	3
external/ring/src/testutil.rs	8
test/spdmlib-test/src/responder_tests/context.rs	15
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
test/spdm-emu/src/async_runtime.rs	3
spdmlib/src/protocol/algo.rs	4
spdmlib/src/secret/mod.rs	3

Fuzzer: finish_req

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	600	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	600	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
599	0	EP	call site: 00000	SpdmKeySchedule::derive_aead_key_iv

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

59

Reachable functions

60

Percentage of reachable functions covered

1.67%

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
spdmlib/fuzz/fuzz_targets/finish_req.rs	4
fuzz-target/requester/psk_finish_req/src/main.rs	22
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	3
spdmlib/src/crypto/bytes_mut_scrubbed.rs	13
test/spdmlib-test/src/common/util.rs	38
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	11
fuzz-target/fuzzlib/src/fake_device_io.rs	2
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
spdmlib/src/common/session.rs	14
spdmlib/src/crypto/mod.rs	5
external/ring/src/testutil.rs	8
test/spdmlib-test/src/responder_tests/context.rs	15
test/spdm-emu/src/async_runtime.rs	3
test/spdmlib-test/src/requester_tests/psk_finish_req.rs	25
spdmlib/src/common/key_schedule.rs	24
test/spdmlib-test/src/common/crypto_callback.rs	3
spdmlib/src/protocol/algo.rs	4
spdmlib/src/secret/mod.rs	3

Fuzzer: encapsulated_request_certificate_req

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	537	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	537	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
536	0	EP	call site: 00000	SpdmCertificateResponsePayload::spdm_read

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

62

Reachable functions

65

Percentage of reachable functions covered

4.62%

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
spdmlib/fuzz/fuzz_targets/encapsulated_request_certificate_req.rs	4
fuzz-target/requester/encapsulated_request_certificate_req/src/main.rs	19
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	3
spdmlib/src/crypto/bytes_mut_scrubbed.rs	8
test/spdmlib-test/src/common/util.rs	42
tdisp/src/pci_tdisp.rs	3
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	12
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	15
test/spdmlib-test/src/common/crypto_callback.rs	3
spdmlib/src/crypto/mod.rs	3
external/ring/src/testutil.rs	8
test/spdmlib-test/src/responder_tests/context.rs	15
test/spdmlib-test/src/common/device_io.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2
spdmlib/src/common/session.rs	6
test/spdm-emu/src/async_runtime.rs	3
test/spdmlib-test/src/requester_tests/encap_certificate.rs	16
spdmlib/src/message/heartbeat.rs	7

Fuzzer: end_session_rsp

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	265	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	265	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
264	0	EP	call site: 00000	fuzz_handle_spdm_end_session

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

52

Reachable functions

55

Percentage of reachable functions covered

5.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.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
spdmlib/fuzz/fuzz_targets/end_session_rsp.rs	4
fuzz-target/responder/end_session_rsp/src/main.rs	16
tdisp/src/pci_tdisp_responder/pci_tdisp_rsp_tdisp_capabilities.rs	2
spdmlib/src/crypto/bytes_mut_scrubbed.rs	7
test/spdmlib-test/src/common/util.rs	19
tdisp/src/pci_tdisp.rs	2
test/spdm-emu/src/crypto_callback.rs	5
test/spdm-emu/src/spdm_emu.rs	7
codec/src/codec.rs	7
spdmlib/src/protocol/mod.rs	6
spdmlib/src/error.rs	2
test/spdm-emu/src/socket_io_transport.rs	10
spdmlib/src/common/session.rs	6
test/spdmlib-test/src/responder_tests/end_session_rsp.rs	20
test/spdm-emu/src/async_runtime.rs	3
spdmlib_crypto_mbedtls/mbedtls-platform-support/src/threading.rs	2