Report generation date: 2025-07-01

Project overview: asn1crypto

High level conclusions

"No files with coverage data was found. This is either because an error occurred when compiling and running coverage runs, or because the introspector run was intentionally done without coverage collection. In order to get optimal results coverage data is needed.

Reachability and coverage overview

Functions statically reachable by fuzzers

3 / 485

Cyclomatic complexity statically reachable by fuzzers

16 / 1794

Runtime code coverage of functions

0 / 485

Fuzzers overview

Fuzzer	Fuzzer filename	Functions Reached	Functions unreached	Fuzzer depth	Files reached	Basic blocks reached	Cyclomatic complexity	Details
fuzz_parse	/src/fuzz_parse.py	9	765	4	4	16	31	fuzz_parse.py

Project functions overview

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 details

Fuzzer: fuzz_parse

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

Full calltree

Call tree overview bitmap:

The project has no code coverage. Will not display blockers as blockers depend on code coverage.

Analyses and suggestions

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	instr count	bb count	cyclomatic complexity	Reachable functions	total cyclomatic complexity	Unreached complexity
`asn1crypto.x509.Name.build`	asn1crypto.x509	3	['N/A', 'N/A', 'N/A']	11	2	5	5	83	344	317
`asn1crypto.x509.URI.__unicode__`	asn1crypto.x509	1	['N/A']	9	1	2	4	79	301	106
`asn1crypto.x509.IPAddress.native`	asn1crypto.x509	1	['N/A']	10	1	7	6	69	280	72
`asn1crypto.x509.URI.set`	asn1crypto.x509	2	['N/A', 'N/A']	3	1	2	4	24	84	63
`asn1crypto.x509.NameTypeAndValue.prepped_value`	asn1crypto.x509	1	['N/A']	2	1	3	4	14	50	44
`asn1crypto.x509.Certificate.is_valid_domain_ip`	asn1crypto.x509	2	['N/A', 'N/A']	2	1	8	6	22	79	42

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

Functions statically reachable by fuzzers

59 / 485

Cyclomatic complexity statically reachable by fuzzers

312 / 1794

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

Fuzz engine guidance

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

/src/fuzz_parse.py

Dictionary

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

Runtime coverage analysis

No runtime coverage data was found

Files and Directories in report

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
	[]	[]
	[]	[]
collections	[]	[]
hashlib	[]	[]
re	[]	[]
fractions	[]	[]
asn1crypto.parser	['fuzz_parse']	[]
datetime	[]	[]
asn1crypto.pem	[]	[]
asn1crypto._errors	[]	[]
asn1crypto.csr	[]	[]
asn1crypto._int	[]	[]
asn1crypto._iri	[]	[]
atheris	[]	[]
asn1crypto.util	['fuzz_parse']	[]
asn1crypto._types	[]	[]
asn1crypto	[]	[]
cStringIO	[]	[]
urlparse	[]	[]
asn1crypto.crl	[]	[]
asn1crypto.version	[]	[]
urllib	[]	[]
stringprep	[]	[]
unicodedata	[]	[]
asn1crypto.ocsp	[]	[]
textwrap	[]	[]
io	[]	[]
asn1crypto.pkcs12	[]	[]
asn1crypto.core	[]	[]
...fuzz_parse	['fuzz_parse']	[]
asn1crypto.tsp	[]	[]
socket	[]	[]
zlib	[]	[]
inspect	[]	[]
asn1crypto.keys	[]	[]
binascii	[]	[]
asn1crypto._inet	[]	[]
asn1crypto.pdf	[]	[]
math	[]	[]
struct	[]	[]
codecs	[]	[]
asn1crypto.algos	[]	[]
base64	[]	[]
asn1crypto._ordereddict	[]	[]
asn1crypto.cms	[]	[]
asn1crypto._teletex_codec	[]	[]
asn1crypto.x509	[]	[]

Directories in report

Directory

Metadata section

This sections shows the raw data that is used to produce this report. This is mainly used for further processing and developer debugging.

Fuzzer Calltree file Program data file Coverage file

fuzz_parse fuzzerLogFile-fuzz_parse.data fuzzerLogFile-fuzz_parse.data.yaml

Table of contents