High level conclusions

Fuzzer fuzz_sign_then_mutate_verify_with_valid_key is blocked:

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

Fuzzer fuzz_simple_sigstore is blocked:

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

Fuzzer fuzz_sign_verify_with_valid_key is blocked:

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

Fuzzer fuzz_sign_with_valid_key_verify_with_invalid_key is blocked:

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

Reachability and coverage overview

Functions statically reachable by fuzzers

70 / 1356

Cyclomatic complexity statically reachable by fuzzers

239 / 4399

Runtime code coverage of functions

345 / 1356

Warning: The number of runtime covered functions are larger than the number of reachable functions. This means that Fuzz Introspector found there are more functions covered at runtime than what is considered reachable based on the static analysis. This is a limitation in the analysis as anything covered at runtime is by definition reachable by the fuzzers.
This is likely due to a limitation in the static analysis. In this case, the count of functions covered at runtime is the true value, which means this is what should be considered "achieved" by the fuzzer.

Use the project functions table below to query all functions that were not covered at runtime.

The following table shows data about each function in the project. The functions included in this table correspond to all functions that exist in the executables of the fuzzers. As such, there may be functions that are from third-party libraries.

For further technical details on the meaning of columns in the below table, please see the Glossary .

Func name	Functions filename	Args	Function call depth	Reached by Fuzzers	Runtime reached by Fuzzers	Combined reached by Fuzzers	Fuzzers runtime hit	Func lines hit %	I Count	BB Count	Cyclomatic complexity	Functions reached	Reached by functions	Accumulated cyclomatic complexity	Undiscovered complexity

Fuzzer: fuzz_sign_with_invalid_key

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	54	69.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	24	30.7%
All colors	78	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
18	55	model_signing._signing.sign_sigstore_pb.pae	call site: 00055	model_signing._signing.sign_pkcs11.CertSigner._get_verification_material
10	20	model_signing.signing.Config.use_elliptic_key_signer	call site: 00020	model_signing.signing.Config.sign
8	41	model_signing.signing.Config.sign	call site: 00041	model_signing._signing.sign_sigstore.Signer._get_identity_token
5	8	...model-transparency.tests.fuzzing.fuzz_sign_with_invalid_key.TestOneInput	call site: 00008	os.path.join
3	0	EP	call site: 00000	atheris.FuzzedDataProvider
3	4	...model-transparency.tests.fuzzing.fuzz_sign_with_invalid_key.TestOneInput	call site: 00004	tempfile.TemporaryDirectory
3	50	model_signing.signing.Config.sign	call site: 00050	model_signing._signing.sign_sigstore_pb.pae
2	16	model_signing.signing.Config.__init__	call site: 00016	model_signing.signing.Config.use_elliptic_key_signer
2	75	model_signing.signing.Config.sign	call site: 00075	cryptography.hazmat.bindings._rust.ObjectIdentifier.to_json

Runtime coverage analysis

Covered functions

434

Functions that are reachable but not covered

48

Reachable functions

69

Percentage of reachable functions covered

30.43%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/	1
...model-transparency.tests.fuzzing.fuzz_sign_with_invalid_key	16
model_signing.signing	10
model_signing._signing.sign_sigstore	16
model_signing._signing.signing	7
model_signing._hashing.memory	1
model_signing._signing.sign_pkcs11	19
model_signing._signing.sign_sigstore_pb	1

Fuzzer: fuzz_sign_with_valid_key_verify_with_invalid_key

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	9	40.9%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	13	59.0%
All colors	22	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
6	1	...model-transparency.tests.fuzzing.fuzz_sign_with_valid_key_verify_with_invalid_key.TestOneInput	call site: 00001	fdp.ConsumeIntInRange
2	14	...model-transparency.tests.fuzzing.fuzz_sign_with_valid_key_verify_with_invalid_key.TestOneInput	call site: 00014	os.path.join
1	20	...model-transparency.tests.fuzzing.fuzz_sign_with_valid_key_verify_with_invalid_key.TestOneInput	call site: 00020	verifier.verify

Runtime coverage analysis

Covered functions

469

Functions that are reachable but not covered

19

Reachable functions

20

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.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/	1
...model-transparency.tests.fuzzing.fuzz_sign_with_valid_key_verify_with_invalid_key	19

Fuzzer: fuzz_sign_verify_with_valid_key

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	3	15.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	17	85.0%
All colors	20	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
2	1	...model-transparency.tests.fuzzing.fuzz_sign_verify_with_valid_key.TestOneInput	call site: 00001	tempfile.TemporaryDirectory
1	16	...model-transparency.tests.fuzzing.fuzz_sign_verify_with_valid_key.TestOneInput	call site: 00016	vcfg.set_hashing_config

Runtime coverage analysis

Covered functions

469

Functions that are reachable but not covered

18

Reachable functions

19

Percentage of reachable functions covered

5.26%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/	1
...model-transparency.tests.fuzzing.fuzz_sign_verify_with_valid_key	18

Fuzzer: fuzz_simple_sigstore

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	154	74.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	52	25.2%
All colors	206	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
41	154	sigstore.oidc.IdentityToken.__init__	call site: 00154	sigstore.oidc.Issuer.identity_token
26	83	sigstore._internal.tuf.TrustUpdater.get_signing_config_path	call site: 00083	sigstore.models.ClientTrustConfig.from_tuf
23	58	sigstore._internal.tuf.TrustUpdater.__init__	call site: 00058	sigstore._internal.tuf.TrustUpdater.get_trusted_root_path
18	127	model_signing._signing.sign_sigstore_pb.pae	call site: 00127	model_signing._signing.sign_pkcs11.CertSigner._get_verification_material
15	1	...model-transparency.tests.fuzzing.fuzz_simple_sigstore.TestOneInput	call site: 00001	sigstore.models.TrustedRoot.from_file
6	46	sigstore._internal.tuf.TrustUpdater.__init__	call site: 00046	sigstore._internal.tuf._get_dirs
4	41	...model-transparency.tests.fuzzing.fuzz_simple_sigstore.TestOneInput	call site: 00041	sigstore.models.ClientTrustConfig.from_tuf
4	149	sigstore.dsse.Statement.__init__	call site: 00149	sigstore.oidc.IdentityToken.__init__
3	54	sigstore._internal.tuf.TrustUpdater.__init__	call site: 00054	urllib.parse.quote
3	122	model_signing.signing.Config.sign	call site: 00122	model_signing._signing.sign_sigstore_pb.pae
2	18	...model-transparency.tests.fuzzing.fuzz_simple_sigstore.TestOneInput	call site: 00018	tempfile.TemporaryDirectory
2	22	...model-transparency.tests.fuzzing.fuzz_simple_sigstore.TestOneInput	call site: 00022	pathlib.Path

Runtime coverage analysis

Covered functions

470

Functions that are reachable but not covered

124

Reachable functions

148

Percentage of reachable functions covered

16.22%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/	1
...model-transparency.tests.fuzzing.fuzz_simple_sigstore	26
sigstore.models	14
model_signing.signing	10
model_signing._signing.sign_sigstore	16
sigstore._internal.tuf	20
sigstore._utils	3
sigstore.oidc	26
sigstore.sign	4
model_signing._signing.signing	7
model_signing._hashing.memory	1
model_signing._signing.sign_pkcs11	19
model_signing._signing.sign_sigstore_pb	2
sigstore.dsse	3
sigstore._internal.oidc.oauth	9

Fuzzer: fuzz_sign_then_mutate_verify_with_valid_key

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	138	70.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	58	29.5%
All colors	196	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
41	136	sigstore.oidc.IdentityToken.__init__	call site: 00136	sigstore.oidc.Issuer.identity_token
26	62	sigstore._internal.tuf.TrustUpdater.get_signing_config_path	call site: 00062	sigstore.models.ClientTrustConfig.from_tuf
23	37	sigstore._internal.tuf.TrustUpdater.__init__	call site: 00037	sigstore._internal.tuf.TrustUpdater.get_trusted_root_path
23	104	model_signing._signing.sign_sigstore_pb.pae	call site: 00104	model_signing._signing.sign_pkcs11.CertSigner._get_verification_material
6	25	sigstore._internal.tuf.TrustUpdater.__init__	call site: 00025	sigstore._internal.tuf._get_dirs
5	19	...model-transparency.tests.fuzzing.fuzz_sign_then_mutate_verify_with_valid_key.TestOneInput	call site: 00019	sigstore.models.ClientTrustConfig.from_tuf
4	131	sigstore.dsse.Statement.__init__	call site: 00131	sigstore.oidc.IdentityToken.__init__
3	33	sigstore._internal.tuf.TrustUpdater.__init__	call site: 00033	urllib.parse.quote
3	99	model_signing.signing.Config.sign	call site: 00099	model_signing._signing.sign_sigstore_pb.pae
2	1	...model-transparency.tests.fuzzing.fuzz_sign_then_mutate_verify_with_valid_key.TestOneInput	call site: 00001	tempfile.TemporaryDirectory
1	128	model_signing.signing.Config.sign	call site: 00128	sigstore.dsse.Statement.__init__
1	181	model_signing.signing.Config.sign	call site: 00181	path.write_text

Runtime coverage analysis

Covered functions

469

Functions that are reachable but not covered

121

Reachable functions

148

Percentage of reachable functions covered

18.24%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/	1
...model-transparency.tests.fuzzing.fuzz_sign_then_mutate_verify_with_valid_key	25
model_signing.signing	11
model_signing._signing.sign_sigstore	16
sigstore.models	11
sigstore._internal.tuf	20
sigstore._utils	3
sigstore.oidc	26
sigstore.sign	4
model_signing._signing.signing	7
model_signing._hashing.memory	1
model_signing._signing.sign_pkcs11	23
model_signing._signing.sign_sigstore_pb	2
sigstore.dsse	3
sigstore._internal.oidc.oauth	9

Fuzzer: fuzz_with_cert_chain

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	111	62.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	67	37.6%
All colors	178	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
62	115	cryptography.x509.extensions.AuthorityKeyIdentifier.__init__	call site: 00115	...model-transparency.tests.fuzzing.fuzz_with_cert_chain.gen_name
18	92	...model-transparency.tests.fuzzing.fuzz_with_cert_chain._pick_sig_hash	call site: 00092	...model-transparency.tests.fuzzing.fuzz_with_cert_chain.gen_name
5	0	EP	call site: 00000	...model-transparency.tests.fuzzing.fuzz_with_cert_chain.build_valid_chain
4	85	cryptography.x509.extensions.SubjectKeyIdentifier.from_public_key	call site: 00085	cryptography.x509.base.CertificateBuilder.sign
3	18	...model-transparency.tests.fuzzing.fuzz_with_cert_chain.gen_name	call site: 00018	fdp.ConsumeIntInRange
3	22	...model-transparency.tests.fuzzing.fuzz_with_cert_chain.gen_name	call site: 00022	...model-transparency.tests.fuzzing.fuzz_with_cert_chain._rand_utf8
3	28	...model-transparency.tests.fuzzing.fuzz_with_cert_chain.gen_name	call site: 00028	fdp.ConsumeBytes
3	73	...model-transparency.tests.fuzzing.fuzz_with_cert_chain.deterministic_serial	call site: 00073	...model-transparency.tests.fuzzing.fuzz_with_cert_chain._ski
3	111	cryptography.x509.extensions.AuthorityKeyIdentifier.from_issuer_subject_key_identifier	call site: 00111	.list
2	32	...model-transparency.tests.fuzzing.fuzz_with_cert_chain.gen_name	call site: 00032	fdp.ConsumeBool
2	81	cryptography.x509.extensions._key_identifier_from_public_key	call site: 00081	public_key.public_bytes
1	8	...model-transparency.tests.fuzzing.fuzz_with_cert_chain.deterministic_validity	call site: 00008	datetime.timedelta

Runtime coverage analysis

Covered functions

473

Functions that are reachable but not covered

48

Reachable functions

75

Percentage of reachable functions covered

36.0%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/	1
...model-transparency.tests.fuzzing.fuzz_with_cert_chain	55
cryptography.hazmat.primitives.asymmetric.rsa	2
cryptography.x509.base	10
cryptography.x509.extensions	9

Optimal target analysis

Remaining optimal interesting functions

The following table shows a list of functions that are optimal targets. Optimal targets are identified by finding the functions that in combination, yield a high code coverage.

Func name	Functions filename	Arg count	Args	Function depth	hitcount	instr count	bb count	cyclomatic complexity	Reachable functions	Incoming references	total cyclomatic complexity	Unreached complexity
sigstore._cli.main	sigstore._cli	1	['N/A']	7	0	13	13	8	242	1	787	512
sigstore.verify.verifier.Verifier.verify_artifact	sigstore.verify.verifier	4	['N/A', 'N/A', 'N/A', 'N/A']	5	0	6	3	4	98	0	315	225
cryptography.hazmat.primitives.serialization.ssh.SSHCertificateBuilder.sign	cryptography.hazmat.primitives.serialization.ssh	2	['N/A', 'N/A']	5	0	37	11	7	52	0	174	141
model_signing._signing.pkcs11uri.Pkcs11URI.login	model_signing._signing.pkcs11uri	1	['N/A']	4	0	2	4	5	31	3	108	90
cryptography.hazmat.primitives.serialization.ssh.load_ssh_private_key	cryptography.hazmat.primitives.serialization.ssh	4	['N/A', 'N/A', 'N/A', 'N/A']	4	0	12	15	9	35	0	116	82
model_signing._serialization.file_shard.Serializer.serialize	model_signing._serialization.file_shard	4	['N/A', 'N/A', 'N/A', 'N/A']	2	0	5	6	5	31	0	99	78
cryptography.fernet.Fernet._decrypt_data	cryptography.fernet	4	['N/A', 'N/A', 'N/A', 'N/A']	4	0	1	3	4	25	2	81	50

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

Functions statically reachable by fuzzers

186 / 1356

Cyclomatic complexity statically reachable by fuzzers

691 / 4399

All functions overview

If you implement fuzzers for these functions, the status of all functions in the project will be:

Func name	Functions filename	Args	Function call depth	Reached by Fuzzers	Runtime reached by Fuzzers	Combined reached by Fuzzers	Fuzzers runtime hit	Func lines hit %	I Count	BB Count	Cyclomatic complexity	Functions reached	Reached by functions	Accumulated cyclomatic complexity	Undiscovered complexity

This sections provides heuristics that can be used as input to a fuzz engine when running a given fuzz target. The current focus is on providing input that is usable by libFuzzer.

/src/model-transparency/tests/fuzzing/fuzz_sign_with_invalid_key.py

Dictionary

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

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['model_signing._signing.sign_sigstore_pb.pae', 'model_signing.signing.Config.use_elliptic_key_signer', 'model_signing.signing.Config.sign', '...model-transparency.tests.fuzzing.fuzz_sign_with_invalid_key.TestOneInput', 'model_signing.signing.Config.__init__']

/src/model-transparency/tests/fuzzing/fuzz_sign_with_valid_key_verify_with_invalid_key.py

Dictionary

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

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['...model-transparency.tests.fuzzing.fuzz_sign_with_valid_key_verify_with_invalid_key.TestOneInput']

/src/model-transparency/tests/fuzzing/fuzz_sign_verify_with_valid_key.py

Dictionary

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

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['...model-transparency.tests.fuzzing.fuzz_sign_verify_with_valid_key.TestOneInput']

/src/model-transparency/tests/fuzzing/fuzz_simple_sigstore.py

Dictionary

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

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['sigstore.oidc.IdentityToken.__init__', 'sigstore._internal.tuf.TrustUpdater.get_signing_config_path', 'sigstore._internal.tuf.TrustUpdater.__init__', 'model_signing._signing.sign_sigstore_pb.pae', '...model-transparency.tests.fuzzing.fuzz_simple_sigstore.TestOneInput', 'sigstore.dsse.Statement.__init__', 'model_signing.signing.Config.sign']

/src/model-transparency/tests/fuzzing/fuzz_sign_then_mutate_verify_with_valid_key.py

Dictionary

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

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['sigstore.oidc.IdentityToken.__init__', 'sigstore._internal.tuf.TrustUpdater.get_signing_config_path', 'sigstore._internal.tuf.TrustUpdater.__init__', 'model_signing._signing.sign_sigstore_pb.pae', '...model-transparency.tests.fuzzing.fuzz_sign_then_mutate_verify_with_valid_key.TestOneInput', 'sigstore.dsse.Statement.__init__', 'model_signing.signing.Config.sign']

/src/model-transparency/tests/fuzzing/fuzz_with_cert_chain.py

Dictionary

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

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['cryptography.x509.extensions.AuthorityKeyIdentifier.__init__', '...model-transparency.tests.fuzzing.fuzz_with_cert_chain._pick_sig_hash', 'cryptography.x509.extensions.SubjectKeyIdentifier.from_public_key', '...model-transparency.tests.fuzzing.fuzz_with_cert_chain.gen_name', '...model-transparency.tests.fuzzing.fuzz_with_cert_chain.deterministic_serial', 'cryptography.x509.extensions.AuthorityKeyIdentifier.from_issuer_subject_key_identifier']

This section shows analysis of runtime coverage data.

For futher technical details on how this section is generated, please see the Glossary .

Complex functions with low coverage

Func name	Function total lines	Lines covered at runtime	percentage covered	Reached by fuzzers
os.path.basename	290	131	45.17%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
cryptography.hazmat.primitives.serialization.ssh.load_ssh_private_key	68	0	0.0%	[]
cryptography.hazmat.primitives.serialization.ssh._serialize_ssh_private_key	52	5	9.615%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
cryptography.hazmat.primitives.serialization.ssh._load_ssh_public_identity	56	0	0.0%	[]
cryptography.hazmat.primitives.serialization.ssh.SSHCertificateBuilder.sign	85	0	0.0%	[]
sigstore.verify.policy.Identity	80	15	18.75%	['fuzz_sign_with_invalid_key']
val.to_bytes	91	38	41.75%	['fuzz_sign_with_invalid_key']
point.tobytes	96	43	44.79%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
typing_extensions.dataclass_transform	1714	560	32.67%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
OpenSSL.crypto.X509StoreContext	880	267	30.34%	['fuzz_sign_with_invalid_key']
resources.append	1640	2	0.121%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
statement.Statement	31	13	41.93%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
asn1crypto.keys.PublicKeyInfo.dump	350	177	50.57%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
asn1crypto.core.OctetString.load	2168	465	21.44%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
google.protobuf.json_format.MessageToJson	500	142	28.4%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
hash.finalize	73	27	36.98%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
i.isdigit	141	16	11.34%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
signer.sign_dsse	89	31	34.83%	['fuzz_simple_sigstore', 'fuzz_sign_with_invalid_key', 'fuzz_sign_then_mutate_verify_with_valid_key']
p.is_absolute	46	21	45.65%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
r.pop	109	13	11.92%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_with_invalid_key', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
signer._signing_cert	89	31	34.83%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
verifier.verify_artifact	235	51	21.70%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
val.lower	91	38	41.75%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
pydantic.model_validator	56	28	50.0%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
jwt.decode	165	37	22.42%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
OpenSSL.crypto.X509StoreContext.get_verified_chain	880	267	30.34%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
response.raise_for_status	728	148	20.32%	['fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_simple_sigstore', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
collections.defaultdict	242	76	31.40%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
url.rstrip	204	60	29.41%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
fields.extend	54	4	7.407%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
sct.log_id.hex	88	21	23.86%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
timestamp.timestamp	46	25	54.34%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
sign.add_argument_group	93	39	41.93%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']
verify.add_subparsers	190	41	21.57%	['fuzz_sign_then_mutate_verify_with_valid_key', 'fuzz_simple_sigstore', 'fuzz_sign_verify_with_valid_key', 'fuzz_with_cert_chain', 'fuzz_sign_with_valid_key_verify_with_invalid_key']

This section shows which files and directories are considered in this report. The main reason for showing this is fuzz introspector may include more code in the reasoning than is desired. This section helps identify if too many files/directories are included, e.g. third party code, which may be irrelevant for the threat model. In the event too much is included, fuzz introspector supports a configuration file that can exclude data from the report. See the following link for more information on how to create a config file: link

Files in report

Source file	Reached by	Covered by
	[]	[]
requests	[]	[]
sigstore.verify.policy	[]	[]
base64	[]	[]
warnings	[]	[]
os	[]	[]
enum	[]	[]
cryptography.hazmat.primitives._cipheralgorithm	[]	[]
pydantic	[]	[]
cryptography.hazmat.primitives.serialization.pkcs12	[]	[]
cryptography.hazmat.primitives.kdf.pbkdf2	[]	[]
rekor_types	[]	[]
json	[]	[]
io	[]	[]
cryptography.x509.base	['fuzz_with_cert_chain']	[]
sigstore.verify.verifier	[]	[]
cryptography.hazmat.primitives.asymmetric.padding	[]	[]
cryptography.hazmat.primitives.asymmetric.utils	[]	[]
cryptography.hazmat.primitives.keywrap	[]	[]
cryptography.hazmat.primitives.kdf.hkdf	[]	[]
cryptography.x509.ocsp	[]	[]
cryptography.hazmat.asn1.asn1	[]	[]
atheris	[]	[]
sigstore._internal.merkle	[]	[]
cryptography.hazmat.primitives.kdf.x963kdf	[]	[]
sigstore._internal.rekor.client_v2	[]	[]
cryptography.hazmat.primitives.ciphers.aead	[]	[]
sigstore.verify	[]	[]
sigstore.oidc	['fuzz_simple_sigstore', 'fuzz_sign_then_mutate_verify_with_valid_key']	[]
sigstore._cli	[]	[]
sigstore.dsse	['fuzz_simple_sigstore', 'fuzz_sign_then_mutate_verify_with_valid_key']	[]
...model-transparency.tests.fuzzing.fuzz_simple_sigstore	['fuzz_simple_sigstore']	[]
cryptography.hazmat.bindings.openssl._conditional	[]	[]
certifi	[]	[]
webbrowser	[]	[]
cryptography	[]	[]
cryptography.__about__	[]	[]
cryptography.hazmat.primitives.serialization.pkcs7	[]	[]
re	[]	[]
cryptography.hazmat.primitives.ciphers	[]	[]
cryptography.hazmat.primitives.ciphers.modes	[]	[]
pyasn1	[]	[]
asn1crypto	[]	[]
cryptography.hazmat.primitives.twofactor.hotp	[]	[]
pathlib	[]	[]
cryptography.hazmat.backends.openssl.backend	[]	[]
cryptography.hazmat.primitives.poly1305	[]	[]
cryptography.hazmat.primitives.asymmetric.ed25519	[]	[]
typing_extensions	[]	[]
cryptography.hazmat.backends.openssl	[]	[]
cryptography.hazmat.asn1	[]	[]
model_signing._hashing.memory	['fuzz_sign_with_invalid_key', 'fuzz_simple_sigstore', 'fuzz_sign_then_mutate_verify_with_valid_key']	[]
rfc3161_client	[]	[]
model_signing._hashing.hashing	[]	[]
stat	[]	[]
glob	[]	[]
cryptography.hazmat.primitives._asymmetric	[]	[]
id	[]	[]
google	[]	[]
model_signing._hashing.io	[]	[]
sigstore._internal.fulcio	[]	[]
cryptography.hazmat.primitives.kdf.concatkdf	[]	[]
sigstore.errors	[]	[]
threading	[]	[]
model_signing._signing	[]	[]
model_signing._serialization	[]	[]
time	[]	[]
functools	[]	[]
PyKCS11	[]	[]
model_signing._serialization.file_shard	[]	[]
cryptography.hazmat.primitives.asymmetric.types	[]	[]
sigstore._utils	['fuzz_simple_sigstore', 'fuzz_sign_then_mutate_verify_with_valid_key']	[]
shutil	[]	[]
cryptography.hazmat.primitives.serialization.base	[]	[]
cryptography.hazmat.primitives.hashes	[]	[]
cryptography.x509.extensions	['fuzz_with_cert_chain']	[]
...model-transparency.tests.fuzzing.fuzz_sign_with_valid_key_verify_with_invalid_key	['fuzz_sign_with_valid_key_verify_with_invalid_key']	[]
cryptography.hazmat.primitives._serialization	[]	[]
sigstore.models	['fuzz_simple_sigstore', 'fuzz_sign_then_mutate_verify_with_valid_key']	[]
sigstore._internal.key_details	[]	[]
cryptography.hazmat.primitives.kdf.kbkdf	[]	[]
types	[]	[]
cryptography.x509.general_name	[]	[]
model_signing._cli	[]	[]
cryptography.hazmat._oid	[]	[]
email	[]	[]
sigstore._internal.sct	[]	[]
	[]	[]
model_signing._serialization.file	[]	[]
cryptography.hazmat.primitives.asymmetric.ec	[]	[]
model_signing._signing.sign_certificate	[]	[]
sigstore._internal.oidc.oauth	['fuzz_simple_sigstore', 'fuzz_sign_then_mutate_verify_with_valid_key']	[]
tuf	[]	[]
cryptography.hazmat.primitives.hmac	[]	[]
sigstore_models	[]	[]
cryptography.hazmat.primitives.asymmetric.dh	[]	[]
uuid	[]	[]
cryptography.hazmat.decrepit.ciphers	[]	[]
sigstore._internal.rekor	[]	[]
cryptography.hazmat	[]	[]
cryptography.hazmat.primitives.constant_time	[]	[]
urllib	[]	[]
sigstore.sign	['fuzz_simple_sigstore', 'fuzz_sign_then_mutate_verify_with_valid_key']	[]
cryptography.hazmat.primitives.twofactor	[]	[]
binascii	[]	[]
typing	[]	[]
cryptography.hazmat.primitives.padding	[]	[]
cryptography.hazmat.primitives.kdf	[]	[]
concurrent	[]	[]
importlib	[]	[]
cryptography.x509	[]	[]
model_signing.signing	['fuzz_sign_with_invalid_key', 'fuzz_simple_sigstore', 'fuzz_sign_then_mutate_verify_with_valid_key']	[]
bcrypt	[]	[]
model_signing.__main__	[]	[]
sigstore.__main__	[]	[]
sys	[]	[]
sigstore._store	[]	[]
model_signing._hashing	[]	[]
cryptography.hazmat.bindings.openssl.binding	[]	[]
sigstore._internal.trust	[]	[]
cryptography.hazmat.primitives.ciphers.base	[]	[]
importlib_resources	[]	[]
hashlib	[]	[]
cryptography.hazmat.primitives.twofactor.totp	[]	[]
cryptography.hazmat.primitives.kdf.argon2	[]	[]
cryptography.hazmat.primitives.kdf.scrypt	[]	[]
cryptography.hazmat.primitives.cmac	[]	[]
model_signing	[]	[]
sigstore._internal.fulcio.client	[]	[]
cryptography.fernet	[]	[]
cryptography.hazmat.primitives	[]	[]
OpenSSL	[]	[]
sigstore	[]	[]
atexit	[]	[]
cryptography.x509.certificate_transparency	[]	[]
cryptography.hazmat.primitives.asymmetric	[]	[]
cryptography.hazmat.bindings._rust	[]	[]
click	[]	[]
tempfile	[]	[]
hmac	[]	[]
...model-transparency.tests.fuzzing.fuzz_sign_then_mutate_verify_with_valid_key	['fuzz_sign_then_mutate_verify_with_valid_key']	[]
cryptography.x509.verification	[]	[]
cryptography.x509.name	[]	[]
...model-transparency.tests.fuzzing.fuzz_sign_verify_with_valid_key	['fuzz_sign_verify_with_valid_key']	[]
...model-transparency.tests.fuzzing.fuzz_sign_with_invalid_key	['fuzz_sign_with_invalid_key']	[]
model_signing.manifest	[]	[]
cryptography.hazmat.primitives.asymmetric.ed448	[]	[]
rich	[]	[]
random	[]	[]
cryptography.hazmat.primitives.ciphers.algorithms	[]	[]
cryptography.exceptions	[]	[]
cryptography.hazmat.primitives.asymmetric.rsa	['fuzz_with_cert_chain']	[]
cryptography.hazmat.bindings	[]	[]
cryptography.hazmat.backends	[]	[]
dataclasses	[]	[]
model_signing._signing.signing	['fuzz_sign_with_invalid_key', 'fuzz_simple_sigstore', 'fuzz_sign_then_mutate_verify_with_valid_key']	[]
rfc8785	[]	[]
cryptography.hazmat.primitives.serialization.ssh	[]	[]
struct	[]	[]
blake3	[]	[]
model_signing._signing.sign_pkcs11	['fuzz_sign_with_invalid_key', 'fuzz_simple_sigstore', 'fuzz_sign_then_mutate_verify_with_valid_key']	[]
cryptography.hazmat.primitives.asymmetric.dsa	[]	[]
jwt	[]	[]
sigstore._internal.oidc	[]	[]
cryptography.x509.oid	[]	[]
model_signing._signing.sign_sigstore	['fuzz_sign_with_invalid_key', 'fuzz_simple_sigstore', 'fuzz_sign_then_mutate_verify_with_valid_key']	[]
sigstore._internal.tuf	['fuzz_simple_sigstore', 'fuzz_sign_then_mutate_verify_with_valid_key']	[]
cryptography.hazmat.primitives.asymmetric.x448	[]	[]
math	[]	[]
sigstore._internal.rekor.checkpoint	[]	[]
argparse	[]	[]
model_signing._serialization.serialization	[]	[]
cryptography.hazmat.decrepit	[]	[]
sigstore._internal.timestamp	[]	[]
...model-transparency.tests.fuzzing.fuzz_with_cert_chain	['fuzz_with_cert_chain']	[]
model_signing._signing.pkcs11uri	[]	[]
datetime	[]	[]
sigstore._internal.rekor.client	[]	[]
textwrap	[]	[]
itertools	[]	[]
cryptography.utils	[]	[]
logging	[]	[]
cryptography.hazmat.primitives.serialization	[]	[]
collections	[]	[]
sigstore.hashes	[]	[]
sigstore.dsse._predicate	[]	[]
opentelemetry	[]	[]
cryptography.hazmat.decrepit.ciphers.algorithms	[]	[]
cryptography.hazmat.bindings.openssl	[]	[]
model_signing._signing.sign_sigstore_pb	['fuzz_sign_with_invalid_key', 'fuzz_simple_sigstore', 'fuzz_sign_then_mutate_verify_with_valid_key']	[]
platformdirs	[]	[]
utils	[]	[]
sigstore._internal	[]	[]
cryptography.hazmat.primitives.asymmetric.x25519	[]	[]

Directories in report

Directory