Fuzz introspector
For issues and ideas: https://github.com/ossf/fuzz-introspector/issues
Project coverage

Table of contents

Project overview: python-ecdsa
High level conclusions
Reachability and coverage overview
Fuzzers overview
Project functions overview
Fuzzer details
Fuzzer: fuzz_eddsa
Call tree
Runtime coverage analysis
Files reached
Fuzzer: fuzz_ecdsa
Call tree
Runtime coverage analysis
Files reached
Fuzzer: fuzz_keys
Call tree
Fuzz blockers
Runtime coverage analysis
Files reached
Analyses and suggestions
Optimal target analysis
Remaining optimal interesting functions
All functions overview
Fuzz engine guidance
/src/fuzz_eddsa.py
Dictionary
Fuzzer function priority
/src/fuzz_ecdsa.py
Dictionary
Fuzzer function priority
/src/fuzz_keys.py
Dictionary
Fuzzer function priority
Runtime coverage analysis
Complex functions with low coverage
Files and Directories in report
Files in report
Directories in report
Metadata section
Report generation date: 2024-07-27

Project overview: python-ecdsa

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
0.0%
0 / 932
Cyclomatic complexity statically reachable by fuzzers
0.0%
0 / 2921
Runtime code coverage of functions
0.0%
1 / 932

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.

Fuzzers overview

Fuzzer Fuzzer filename Functions Reached Functions unreached Fuzzer depth Files reached Basic blocks reached Cyclomatic complexity Details
fuzz_eddsa /src/fuzz_eddsa.py 3 1271 1 2 0 6 fuzz_eddsa.py
fuzz_ecdsa /src/fuzz_ecdsa.py 3 1271 1 2 0 6 fuzz_ecdsa.py
fuzz_keys /src/fuzz_keys.py 3 1279 1 2 0 6 fuzz_keys.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 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_eddsa

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 distribution of callsites in terms of coloring is
Color Runtime hitcount Callsite count Percentage
red 0 0 0.0%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 3 100.%
All colors 3 100

Runtime coverage analysis

Covered functions
7
Functions that are reachable but not covered
3
Reachable functions
3
Percentage of reachable functions covered
0.0%
NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.
Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.
Function name source code lines source lines hit percentage hit

Files reached

filename functions hit
/ 1
...fuzz_eddsa 2

Fuzzer: fuzz_ecdsa

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 distribution of callsites in terms of coloring is
Color Runtime hitcount Callsite count Percentage
red 0 0 0.0%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 3 100.%
All colors 3 100

Runtime coverage analysis

Covered functions
7
Functions that are reachable but not covered
3
Reachable functions
3
Percentage of reachable functions covered
0.0%
NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.
Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.
Function name source code lines source lines hit percentage hit

Files reached

filename functions hit
/ 1
...fuzz_ecdsa 2

Fuzzer: fuzz_keys

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 distribution of callsites in terms of coloring is
Color Runtime hitcount Callsite count Percentage
red 0 3 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 3 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 0 EP call site: 00000 atheris.FuzzedDataProvider

Runtime coverage analysis

Covered functions
7
Functions that are reachable but not covered
3
Reachable functions
3
Percentage of reachable functions covered
0.0%
NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.
Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.
Function name source code lines source lines hit percentage hit

Files reached

filename functions hit
/ 1
...fuzz_keys 2

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 hitcount instr count bb count cyclomatic complexity Reachable functions Incoming references total cyclomatic complexity Unreached complexity
ecdsa.test_ecdh.test_ecdh_with_openssl ecdsa.test_ecdh 1 ['N/A'] 9 0 16 4 5 144 0 479 479
ecdsa.ecdsa.Public_key.verifies ecdsa.ecdsa 3 ['N/A', 'N/A', 'N/A'] 5 0 1 3 4 68 11 222 99
ecdsa.ellipticcurve.AbstractPoint.from_bytes ecdsa.ellipticcurve 5 ['N/A', 'N/A', 'N/A', 'N/A', 'N/A'] 5 0 1 8 6 40 0 137 61
ecdsa.curves.Curve.to_der ecdsa.curves 3 ['N/A', 'N/A', 'N/A'] 5 0 2 7 6 65 9 206 58
ecdsa.test_numbertheory.TestNumbertheory.test_jacobi ecdsa.test_numbertheory 2 ['N/A', 'N/A'] 4 0 1 2 4 21 0 78 39
ecdsa.keys.SigningKey.sign_number ecdsa.keys 4 ['N/A', 'N/A', 'N/A', 'N/A'] 3 0 1 2 4 18 4 59 35

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

Functions statically reachable by fuzzers
12.0%
110 / 932
Cyclomatic complexity statically reachable by fuzzers
14.0%
418 / 2921

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 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_eddsa.py

Dictionary

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


/src/fuzz_ecdsa.py

Dictionary

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


/src/fuzz_keys.py

Dictionary

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


Runtime coverage analysis

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
six.next 501 252 50.29% []
l.startswith 165 48 29.09% []
t.join 79 23 29.11% []

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
[] []
ecdsa.test_ellipticcurve [] []
json [] []
warnings [] []
ecdsa.test_curves [] []
math [] []
binascii [] []
[] []
ecdsa.keys [] []
...fuzz_keys ['fuzz_keys'] []
ecdsa.rfc6979 [] []
unittest [] []
pickle [] []
ecdsa.util [] []
gmpy [] []
ecdsa.ecdh [] []
ecdsa.curves [] []
itertools [] []
...fuzz_ecdsa ['fuzz_ecdsa'] []
ecdsa.test_sha3 [] []
ecdsa.test_ecdsa [] []
_sha3 [] []
ecdsa._compat [] []
platform [] []
hypothesis [] []
ecdsa._version [] []
re [] []
os [] []
gmpy2 [] []
shutil [] []
ecdsa.der [] []
hashlib [] []
ecdsa.ellipticcurve [] []
atheris [] []
pytest [] []
ecdsa.test_der [] []
subprocess [] []
ecdsa.test_pyecdsa [] []
base64 [] []
hmac [] []
ecdsa [] []
ecdsa.test_keys [] []
ecdsa.test_malformed_sigs [] []
functools [] []
random [] []
...fuzz_eddsa ['fuzz_eddsa'] []
ecdsa.errors [] []
threading [] []
ecdsa.test_eddsa [] []
ecdsa.eddsa [] []
ecdsa.ecdsa [] []
six [] []
ecdsa.test_jacobi [] []
ecdsa.test_numbertheory [] []
ecdsa.ssh [] []
ecdsa._sha3 [] []
array [] []
unittest2 [] []
ecdsa.numbertheory [] []
ecdsa.test_ecdh [] []

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_eddsa fuzzerLogFile-fuzz_eddsa.data fuzzerLogFile-fuzz_eddsa.data.yaml all_cov.json
fuzz_ecdsa fuzzerLogFile-fuzz_ecdsa.data fuzzerLogFile-fuzz_ecdsa.data.yaml all_cov.json
fuzz_keys fuzzerLogFile-fuzz_keys.data fuzzerLogFile-fuzz_keys.data.yaml all_cov.json