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

Table of contents

Project overview: qpid-proton
High level conclusions
Reachability and coverage overview
Fuzzers overview
Project functions overview
Fuzzer details
Fuzzer: c/tests/fuzz/fuzz-sniff-header.c
Call tree
Fuzzer: c/tests/fuzz/fuzz-url.c
Call tree
Fuzzer: fuzz-message-decode
Call tree
Fuzzer: fuzz-connection-driver
Call tree
Analyses and suggestions
Optimal target analysis
Remaining optimal interesting functions
All functions overview
Fuzz engine guidance
c/tests/fuzz/fuzz-sniff-header.c
Dictionary
Fuzzer function priority
c/tests/fuzz/fuzz-url.c
Dictionary
Fuzzer function priority
c/tests/fuzz/fuzz-message-decode.c
Dictionary
Fuzzer function priority
c/tests/fuzz/fuzz-connection-driver.c
Dictionary
Fuzzer function priority
Runtime coverage analysis
Files and Directories in report
Files in report
Directories in report
Metadata section
Report generation date: 2025-02-21

Project overview: qpid-proton

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
28.9%
373 / 1269
Cyclomatic complexity statically reachable by fuzzers
28.0%
1494 / 5344
Runtime code coverage of functions
0.0%
0 / 1269

Fuzzers overview

Fuzzer Fuzzer filename Functions Reached Functions unreached Fuzzer depth Files reached Basic blocks reached Cyclomatic complexity Details
c/tests/fuzz/fuzz-sniff-header.c c/tests/fuzz/fuzz-sniff-header.c 2 1 1 2 92 43 fuzz-sniff-header.c
c/tests/fuzz/fuzz-url.c c/tests/fuzz/fuzz-url.c 34 94 8 6 203 115 fuzz-url.c
fuzz-message-decode c/tests/fuzz/fuzz-message-decode.c 102 1225 9 13 820 381 fuzz-message-decode.c
fuzz-connection-driver c/tests/fuzz/fuzz-connection-driver.c 380 981 15 26 2939 1449 fuzz-connection-driver.c

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: c/tests/fuzz/fuzz-sniff-header.c

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.

Fuzzer: c/tests/fuzz/fuzz-url.c

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.

Fuzzer: fuzz-message-decode

Call tree

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

Full calltree

Call tree overview bitmap:

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

Fuzzer: fuzz-connection-driver

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 hitcount instr count bb count cyclomatic complexity Reachable functions Incoming references total cyclomatic complexity Unreached complexity
pn_output_write_amqp /src/qpid-proton/c/src/core/transport.c 4 ['N/A', 'int', 'N/A', 'size_t'] 19 0 73 16 7 306 0 1428 988
pn_data_scan /src/qpid-proton/c/src/core/codec.c 2 ['N/A', 'N/A'] 9 0 21 3 2 102 0 507 268
pn_ssl_init /src/qpid-proton/c/src/ssl/openssl.c 3 ['N/A', 'N/A', 'N/A'] 8 0 107 23 10 90 0 280 243
pn_output_write_sasl /src/qpid-proton/c/src/sasl/sasl.c 4 ['N/A', 'int', 'N/A', 'size_t'] 13 0 116 22 10 163 0 702 127
pn_data_vfill /src/qpid-proton/c/src/core/codec.c 3 ['N/A', 'N/A', 'N/A'] 11 0 1093 187 59 114 3 520 122
pn_message_send /src/qpid-proton/c/src/core/message.c 3 ['N/A', 'N/A', 'N/A'] 12 0 77 14 6 135 0 491 118
pn_do_attach /src/qpid-proton/c/src/core/transport.c 5 ['N/A', 'char', 'short', 'size_t', 'N/A'] 11 0 524 50 19 122 0 433 79
pn_io_layer_input_autodetect /src/qpid-proton/c/src/core/transport.c 4 ['N/A', 'int', 'N/A', 'size_t'] 11 0 327 60 21 77 0 319 78
pn_do_mechanisms /src/qpid-proton/c/src/sasl/sasl.c 5 ['N/A', 'char', 'short', 'size_t', 'N/A'] 10 0 257 51 20 71 0 278 76
process_input_ssl /src/qpid-proton/c/src/ssl/openssl.c 4 ['N/A', 'int', 'N/A', 'size_t'] 12 0 434 74 31 85 0 305 72

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

Functions statically reachable by fuzzers
56.0%
711 / 1269
Cyclomatic complexity statically reachable by fuzzers
65.0%
3456 / 5344

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.

c/tests/fuzz/fuzz-sniff-header.c

Dictionary

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


c/tests/fuzz/fuzz-url.c

Dictionary

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


c/tests/fuzz/fuzz-message-decode.c

Dictionary

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


c/tests/fuzz/fuzz-connection-driver.c

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
[] []
/src/qpid-proton/c/src/core/decoder.c ['fuzz-connection-driver'] []
/src/qpid-proton/c/src/core/connection_driver.c ['fuzz-connection-driver'] []
/src/qpid-proton/build/c/src/extra/url.c ['c/tests/fuzz/fuzz-url.c'] []
/src/qpid-proton/c/src/core/memory.c ['fuzz-message-decode', 'fuzz-connection-driver'] []
/src/qpid-proton/c/src/core/consumers.h ['fuzz-message-decode', 'fuzz-connection-driver'] []
/src/qpid-proton/c/src/core/codec.c ['fuzz-message-decode', 'fuzz-connection-driver'] []
/src/qpid-proton/c/src/core/util.c ['fuzz-message-decode', 'fuzz-connection-driver'] []
/src/qpid-proton/c/src/core/dispatcher.c [] []
/src/qpid-proton/c/src/core/error.c ['fuzz-message-decode', 'fuzz-connection-driver'] []
/src/qpid-proton/c/src/core/value_dump.c [] []
/src/qpid-proton/c/src/core/util.h ['fuzz-message-decode', 'fuzz-connection-driver'] []
/src/qpid-proton/c/src/core/message.c ['fuzz-message-decode', 'fuzz-connection-driver'] []
/src/qpid-proton/c/src/core/framing.c [] []
/usr/include/openssl/x509v3.h [] []
/src/qpid-proton/build/c/src/core/autodetect.c ['c/tests/fuzz/fuzz-sniff-header.c'] []
/src/qpid-proton/c/tests/fuzz/fuzz-sniff-header.c ['c/tests/fuzz/fuzz-sniff-header.c'] []
/src/qpid-proton/build/c/src/core/frame_generators.c [] []
/src/qpid-proton/c/src/core/transport.c ['fuzz-connection-driver'] []
/src/qpid-proton/build/c/src/core/object/string.c ['c/tests/fuzz/fuzz-url.c'] []
/src/qpid-proton/c/tests/fuzz/fuzz-connection-driver.c ['fuzz-connection-driver'] []
/src/qpid-proton/c/src/core/object/record.c ['fuzz-connection-driver'] []
/src/qpid-proton/c/src/core/event.c ['fuzz-connection-driver'] []
/src/qpid-proton/build/c/src/core/memory.c ['c/tests/fuzz/fuzz-url.c'] []
/src/qpid-proton/c/src/core/object/list.c ['fuzz-connection-driver'] []
/src/qpid-proton/c/src/core/logger.c ['fuzz-connection-driver'] []
/src/qpid-proton/c/tests/fuzz/fuzz-url.c ['c/tests/fuzz/fuzz-url.c'] []
/src/qpid-proton/c/src/core/engine.c ['fuzz-connection-driver'] []
/src/qpid-proton/c/src/core/encoder.c [] []
/src/qpid-proton/build/c/src/core/util.c ['c/tests/fuzz/fuzz-url.c'] []
/src/qpid-proton/c/src/core/autodetect.c [] []
/src/qpid-proton/c/src/core/object/iterator.c [] []
/src/qpid-proton/c/src/core/object/map.c ['fuzz-connection-driver'] []
/src/qpid-proton/c/src/core/object/object.c ['fuzz-message-decode', 'fuzz-connection-driver'] []
/src/qpid-proton/c/src/core/data.h ['fuzz-message-decode', 'fuzz-connection-driver'] []
/src/qpid-proton/c/src/core/emitters.h [] []
/usr/include/x86_64-linux-gnu/sys/stat.h [] []
/src/qpid-proton/c/src/sasl/cyrus_stub.c [] []
/src/qpid-proton/c/src/core/object/string.c ['fuzz-message-decode', 'fuzz-connection-driver'] []
/src/qpid-proton/c/src/ssl/openssl.c ['fuzz-connection-driver'] []
/src/qpid-proton/build/c/src/core/object/object.c ['c/tests/fuzz/fuzz-url.c'] []
/src/qpid-proton/build/c/src/core/frame_consumers.c ['fuzz-message-decode', 'fuzz-connection-driver'] []
/src/qpid-proton/c/src/core/buffer.c ['fuzz-message-decode', 'fuzz-connection-driver'] []
/src/qpid-proton/c/tests/fuzz/fuzz-message-decode.c ['fuzz-message-decode'] []
/src/qpid-proton/c/include/proton/types.h ['fuzz-connection-driver'] []
/src/qpid-proton/c/src/core/fixed_string.h ['fuzz-connection-driver'] []
/src/qpid-proton/c/src/sasl/default_sasl.c [] []
/src/qpid-proton/c/src/sasl/sasl.c ['fuzz-connection-driver'] []

Directories in report

Directory
/src/qpid-proton/build/c/src/extra/
/src/qpid-proton/c/src/sasl/
/src/qpid-proton/c/src/ssl/
/src/qpid-proton/c/tests/fuzz/
/src/qpid-proton/build/c/src/core/object/
/src/qpid-proton/c/src/core/object/
/src/qpid-proton/c/src/core/
/src/qpid-proton/c/include/proton/
/usr/include/openssl/
/src/qpid-proton/build/c/src/core/
/usr/include/x86_64-linux-gnu/sys/

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
c/tests/fuzz/fuzz-sniff-header.c fuzzerLogFile-0-5bXP0hQJoP.data fuzzerLogFile-0-5bXP0hQJoP.data.yaml
c/tests/fuzz/fuzz-url.c fuzzerLogFile-0-zKkbkWLw44.data fuzzerLogFile-0-zKkbkWLw44.data.yaml
fuzz-message-decode fuzzerLogFile-0-s54EJ6Wg3p.data fuzzerLogFile-0-s54EJ6Wg3p.data.yaml
fuzz-connection-driver fuzzerLogFile-0-s4uXyAj8ef.data fuzzerLogFile-0-s4uXyAj8ef.data.yaml