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

Table of contents

Project overview: cpp-httplib
High level conclusions
Reachability and coverage overview
Fuzzers overview
Project functions overview
Fuzzer details
Fuzzer: server_fuzzer
Call tree
Analyses and suggestions
Optimal target analysis
Remaining optimal interesting functions
All functions overview
Fuzz engine guidance
/src/cpp-httplib/test/fuzzing/server_fuzzer.cc
Dictionary
Fuzzer function priority
Runtime coverage analysis
Files and Directories in report
Files in report
Directories in report
Metadata section
Report generation date: 2025-07-01

Project overview: cpp-httplib

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
41.0%
159 / 388
Cyclomatic complexity statically reachable by fuzzers
56.9%
1611 / 2822
Runtime code coverage of functions
0.0%
0 / 388

Fuzzers overview

Fuzzer Fuzzer filename Functions Reached Functions unreached Fuzzer depth Files reached Basic blocks reached Cyclomatic complexity Details
server_fuzzer /src/cpp-httplib/test/fuzzing/server_fuzzer.cc 334 281 11 2 2631 1649 server_fuzzer.cc

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

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
httplib::Server::read_content_core(httplib::Stream&,httplib::Request&,httplib::Response&,std::__1::function ,std::__1::function ,std::__1::function )const::{lambda(charconst*,unsignedlong,unsignedlong,unsignedlong)#1}::operator()(charconst*,unsignedlong,unsignedlong,unsignedlong)const /src/cpp-httplib/test/fuzzing/../../httplib.h 5 ['N/A', 'N/A', 'size_t', 'size_t', 'size_t'] 6 0 36 3 2 76 0 296 195
LLVMFuzzerInitialize /src/cpp-httplib/test/fuzzing/server_fuzzer.cc 2 ['N/A', 'N/A'] 6 0 201 34 23 33 0 137 137
httplib::ClientImpl::create_and_connect_socket(httplib::ClientImpl::Socket&,httplib::Error&) /src/cpp-httplib/test/fuzzing/../../httplib.h 3 ['N/A', 'N/A', 'N/A'] 9 0 46 6 3 56 0 125 121
httplib::Server::process_and_close_socket(int) /src/cpp-httplib/test/fuzzing/../../httplib.h 2 ['N/A', 'int'] 15 0 112 11 8 370 0 1721 78
httplib::detail::parse_accept_header(std::__1::basic_string ,std::__1::allocator >const&,std::__1::vector ,std::__1::allocator >,std::__1::allocator ,std::__1::allocator >>>&)::{lambda(charconst*,charconst*)#1}::operator()(charconst*,charconst*)const /src/cpp-httplib/test/fuzzing/../../httplib.h 3 ['N/A', 'N/A', 'N/A'] 3 0 362 63 61 12 0 79 65
httplib::detail::write_content_chunked ,std::__1::allocator >const&,std::__1::basic_string ,std::__1::allocator >const&)::{lambda()#1},httplib::detail::compressor>(httplib::Stream&,std::__1::function const&,httplib::Server::write_content_with_provider(httplib::Stream&,httplib::Requestconst&,httplib::Response&,std::__1::basic_string ,std::__1::allocator >const&,std::__1::basic_string ,std::__1::allocator >const&)::{lambda()#1}const&,httplib::detail::compressor&,httplib::Error&)::{lambda(std::__1::unordered_multimap ,std::__1::allocator >,std::__1::basic_string ,std::__1::allocator >,httplib::detail::case_ignore::hash,std::__1::unordered_multimap::equal_to,std::__1::allocator ,std::__1::allocator >const,std::__1::basic_string ,std::__1::allocator >>>>const&)#1}::operator()(std::__1::unordered_multimap ,std::__1::allocator >,std::__1::basic_string ,std::__1::allocator >,httplib::detail::case_ignore::hash,std::__1::unordered_multimap::equal_to,std::__1::allocator ,std::__1::allocator >const,std::__1::basic_string ,std::__1::allocator >>>>const)const /src/cpp-httplib/test/fuzzing/../../httplib.h 2 ['N/A', 'N/A'] 2 0 22 3 2 10 0 69 63
httplib::detail::SocketStream::write(charconst*,unsignedlong) /src/cpp-httplib/test/fuzzing/../../httplib.h 3 ['N/A', 'N/A', 'size_t'] 8 0 40 6 3 38 0 57 41

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

Functions statically reachable by fuzzers
65.0%
252 / 388
Cyclomatic complexity statically reachable by fuzzers
80.0%
2261 / 2822

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/cpp-httplib/test/fuzzing/server_fuzzer.cc

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/cpp-httplib/test/fuzzing/../../httplib.h ['server_fuzzer'] []
/usr/local/bin/../include/c++/v1/string [] []
/src/cpp-httplib/test/fuzzing/server_fuzzer.cc ['server_fuzzer'] []
/usr/local/bin/../include/c++/v1/__exception/exception.h [] []
/usr/local/bin/../include/c++/v1/stdexcept [] []

Directories in report

Directory
/src/cpp-httplib/test/fuzzing/
/src/cpp-httplib/test/fuzzing/../../
/usr/local/bin/../include/c++/v1/__exception/
/usr/local/bin/../include/c++/v1/

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
server_fuzzer fuzzerLogFile-0-ydVPgkVjek.data fuzzerLogFile-0-ydVPgkVjek.data.yaml