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

Table of contents

Project overview: flask-restx
High level conclusions
Reachability and coverage overview
Fuzzers overview
Project functions overview
Fuzzer details
Fuzzer: fuzz_reqparse
Call tree
Fuzz blockers
Runtime coverage analysis
Files reached
Analyses and suggestions
Optimal target analysis
Remaining optimal interesting functions
All functions overview
Runtime coverage analysis
Complex functions with low coverage
Files and Directories in report
Files in report
Directories in report
Metadata section
Function call coverage
Function in each files in report
Report generation date: 2023-09-25

Project overview: flask-restx

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
5.0%
84 / 1655
Cyclomatic complexity statically reachable by fuzzers
6.0%
322 / 5677
Runtime code coverage of functions
24.0%
392 / 1655

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_reqparse /src/fuzz_reqparse.py 222 2802 10 16 190 733 fuzz_reqparse.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_reqparse

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 324 65.7%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 169 34.2%
All colors 493 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
42 274 werkzeug._internal._to_bytes call site: 00274 werkzeug.datastructures.Headers.__init__
40 214 werkzeug.datastructures.Headers.extend call site: 00214 werkzeug.datastructures.Headers.__init__
34 418 werkzeug._internal._encode_idna call site: 00418 werkzeug.routing.Map.bind
31 330 werkzeug.urls.url_encode call site: 00330 werkzeug.urls.url_join
25 188 werkzeug.datastructures.iter_multi_items call site: 00188 werkzeug.datastructures.Headers.add
16 76 werkzeug.urls.url_unparse call site: 00076 werkzeug._internal._to_str
15 125 werkzeug.urls.iri_to_uri call site: 00125 werkzeug.urls.url_fix
15 143 werkzeug.datastructures.MultiDict.__init__ call site: 00143 werkzeug.datastructures.OrderedMultiDict.lists
14 22 werkzeug._internal._to_str call site: 00022 werkzeug.urls.BaseURL.decode_netloc
14 256 werkzeug.test.EnvironBuilder.get_request call site: 00256 werkzeug.test.stream_encode_multipart
14 402 flask.ctx.AppContext.__init__ call site: 00402 werkzeug.routing.Map.bind_to_environ
8 321 werkzeug.urls._url_encode_impl call site: 00321 werkzeug.urls._fast_url_quote_plus

Runtime coverage analysis

Covered functions
489
Functions that are reachable but not covered
172
Reachable functions
222
Percentage of reachable functions covered
22.52%
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_reqparse 9
werkzeug.wrappers.request 9
werkzeug.test 53
werkzeug._internal 17
werkzeug.urls 62
werkzeug.datastructures 43
werkzeug.http 10
werkzeug.sansio.multipart 4
werkzeug.wsgi 4
flask.app 3
flask.ctx 1
werkzeug.routing 20
werkzeug.sansio.utils 7
flask_restx.reqparse 16
flask_restx.errors 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
werkzeug.debug.DebuggedApplication.__call__ werkzeug.debug 3 ['N/A', 'N/A', 'N/A'] 9 0 1 6 5 346 0 1141 762
flask_restx.swagger.Swagger.as_dict flask_restx.swagger 1 ['N/A'] 4 0 2 9 7 96 1 330 270
flask.app.Flask.run flask.app 6 ['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A'] 6 0 8 10 7 108 0 350 233
werkzeug.wrappers.response.Response.make_conditional werkzeug.wrappers.response 4 ['N/A', 'N/A', 'N/A', 'N/A'] 9 0 1 6 5 92 0 313 217
werkzeug.formparser.exhaust_stream.wrapper werkzeug.formparser 4 ['N/A', 'N/A', 'N/A', 'N/A'] 8 0 1 2 4 148 0 486 214
flask_restx.reqparse.Argument.parse flask_restx.reqparse 3 ['N/A', 'N/A', 'N/A'] 7 0 3 15 9 94 0 319 153
flask.app.Flask.handle_exception flask.app 2 ['N/A', 'N/A'] 9 0 3 3 4 86 2 291 133

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

Functions statically reachable by fuzzers
19.0%
320 / 1655
Cyclomatic complexity statically reachable by fuzzers
22.0%
1257 / 5677

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

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
flask.app.Flask.run 34 0 0.0% []
flask.app.Flask.make_response 32 0 0.0% []
flask_restx.reqparse.Argument.parse 48 26 54.16% []
werkzeug.serving.WSGIRequestHandler.make_environ 33 0 0.0% []
werkzeug.serving.BaseWSGIServer.__init__ 34 0 0.0% []
werkzeug.urls.url_join 40 0 0.0% ['fuzz_reqparse']
werkzeug.wsgi.extract_path_info._normalize_netloc 32 2 6.25% []
werkzeug.wsgi.make_line_iter._iter_basic_lines 32 0 0.0% []
werkzeug.wsgi.make_chunk_iter 38 2 5.263% []
flask.cli.find_app_by_string 34 0 0.0% []
werkzeug.utils.send_file 81 0 0.0% []
werkzeug.http.parse_options_header 47 8 17.02% []
werkzeug.http.parse_range_header 38 0 0.0% []
werkzeug.http.dump_cookie 39 0 0.0% []
time.sleep 77 14 18.18% []
werkzeug.wrappers.response.Response.get_wsgi_headers 37 0 0.0% []
re.split 1169 359 30.71% []
safe.encode 41 17 41.46% ['fuzz_reqparse']
p.get 54 9 16.66% []
werkzeug.sansio.multipart.MultipartDecoder.next_event 48 0 0.0% []
werkzeug.routing.Rule.match 33 0 0.0% []
werkzeug.routing.MapAdapter.match 36 0 0.0% []
werkzeug.test.stream_encode_multipart.write_binary 38 0 0.0% ['fuzz_reqparse']
werkzeug.test.EnvironBuilder.__init__ 65 35 53.84% ['fuzz_reqparse']
werkzeug.test.Client.open 34 0 0.0% []
val.split 146 16 10.95% []
info.load_app 37 16 43.24% []
flask.blueprints.Blueprint.register.extend 39 0 0.0% []
r.as_dict 252 43 17.06% []
sources.append 1578 2 0.126% []
flask_restx.inputs.URL.__call__ 45 0 0.0% []
flask.helpers.url_for 40 0 0.0% []
pytz.UTC.localize 202 77 38.11% []
jinja2.utils.htmlsafe_json_dumps 315 104 33.01% []
types.MethodType 420 162 38.57% []
markupsafe.Markup 162 78 48.14% []
flask_restx.api.Api.__init__ 43 0 0.0% []
flask_restx.api.Api.handle_error 45 0 0.0% []
flask_restx.swagger.Swagger.as_dict 33 0 0.0% []
flask_restx.swagger.Swagger.extract_resource_doc 42 0 0.0% []
flask_restx.swagger.Swagger.responses_for 42 0 0.0% []

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
[] []
werkzeug.serving [] []
markupsafe [] []
flask.signals [] []
flask.sessions [] []
secrets [] []
termios [] []
flask_restx [] []
flask_restx.swagger [] []
typing [] []
werkzeug.debug.console [] []
socket [] []
flask.logging [] []
time [] []
flask_restx.errors ['fuzz_reqparse'] []
mimetypes [] []
werkzeug.debug [] []
asgiref [] []
flask_restx.fields [] []
ast [] []
functools [] []
ssl [] []
random [] []
threading [] []
pkgutil [] []
dotenv [] []
werkzeug.datastructures ['fuzz_reqparse'] []
logging [] []
werkzeug._internal ['fuzz_reqparse'] []
json [] []
flask.typing [] []
ntpath [] []
werkzeug.sansio.response [] []
flask_restx.mask [] []
werkzeug.utils [] []
types [] []
contextvars [] []
werkzeug.middleware.proxy_fix [] []
readline [] []
flask.ctx ['fuzz_reqparse'] []
flask_restx.reqparse ['fuzz_reqparse'] []
warnings [] []
unicodedata [] []
itertools [] []
flask.debughelpers [] []
[] []
operator [] []
base64 [] []
werkzeug.wrappers.response [] []
werkzeug.debug.tbtools [] []
flask_restx.model [] []
pstats [] []
string [] []
decimal [] []
flask.json [] []
datetime [] []
cProfile [] []
flask_restx._http [] []
dataclasses [] []
http [] []
werkzeug.sansio [] []
html [] []
flask_restx.__about__ [] []
flask.app ['fuzz_reqparse'] []
werkzeug.exceptions [] []
werkzeug [] []
werkzeug.sansio.multipart ['fuzz_reqparse'] []
jsonschema [] []
re [] []
werkzeug.sansio.utils ['fuzz_reqparse'] []
atexit [] []
rlcompleter [] []
importlib_resources [] []
werkzeug._reloader [] []
werkzeug.wrappers.request ['fuzz_reqparse'] []
collections [] []
werkzeug.middleware.lint [] []
flask.scaffold [] []
flask_restx.resource [] []
flask_restx.apidoc [] []
inspect [] []
math [] []
blinker [] []
email [] []
werkzeug.middleware.shared_data [] []
copy [] []
werkzeug.testapp [] []
flask.__main__ [] []
urllib [] []
werkzeug.formparser [] []
pprint [] []
flask.cli [] []
tempfile [] []
flask.config [] []
flask.views [] []
flask.wrappers [] []
werkzeug.wrappers [] []
codecs [] []
colorama [] []
flask.templating [] []
flask_restx.utils [] []
werkzeug.http ['fuzz_reqparse'] []
werkzeug.wsgi ['fuzz_reqparse'] []
flask.helpers [] []
itsdangerous [] []
werkzeug.middleware [] []
flask_restx.namespace [] []
shutil [] []
linecache [] []
flask_restx.api [] []
flask_restx.cors [] []
jinja2 [] []
sys [] []
enum [] []
flask.globals [] []
platform [] []
ujson [] []
weakref [] []
uuid [] []
werkzeug.middleware.profiler [] []
posixpath [] []
flask.testing [] []
pytz [] []
flask.json.tag [] []
werkzeug.routing ['fuzz_reqparse'] []
cryptography [] []
os [] []
werkzeug.user_agent [] []
hmac [] []
importlib [] []
signal [] []
werkzeug.security [] []
traceback [] []
io [] []
pathlib [] []
flask_restx.representations [] []
flask [] []
code [] []
calendar [] []
zlib [] []
winreg [] []
...fuzz_reqparse ['fuzz_reqparse'] []
werkzeug.middleware.http_proxy [] []
flask.blueprints [] []
subprocess [] []
flask_restx.postman [] []
profile [] []
werkzeug.test ['fuzz_reqparse'] []
werkzeug.sansio.request [] []
fnmatch [] []
flask_restx.marshalling [] []
pydoc [] []
werkzeug.local [] []
aniso8601 [] []
flask_restx.schemas [] []
difflib [] []
werkzeug.debug.repr [] []
flask_restx.inputs [] []
textwrap [] []
werkzeug.middleware.dispatcher [] []
sysconfig [] []
click [] []
watchdog [] []
werkzeug.urls ['fuzz_reqparse'] []
importlib_metadata [] []
getpass [] []
atheris [] []
hashlib [] []

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_reqparse fuzzerLogFile-fuzz_reqparse.data fuzzerLogFile-fuzz_reqparse.data.yaml all_cov.json