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

Table of contents

Project overview: ntlm2
High level conclusions
Reachability and coverage overview
Fuzzers overview
Project functions overview
Fuzzer details
Fuzzer: fuzz_core
Call tree
Runtime coverage analysis
Files reached
Fuzzer: fuzz_auth
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: ntlm2

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
26.0%
74 / 282
Cyclomatic complexity statically reachable by fuzzers
28.0%
277 / 976
Runtime code coverage of functions
13.0%
36 / 282

Fuzzers overview

Fuzzer Fuzzer filename Functions Reached Functions unreached Fuzzer depth Files reached Basic blocks reached Cyclomatic complexity Details
fuzz_core /src/fuzz_core.py 13 668 3 3 4 38 fuzz_core.py
fuzz_auth /src/fuzz_auth.py 245 445 8 12 151 786 fuzz_auth.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_core

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+ 16 100.%
All colors 16 100

Runtime coverage analysis

Covered functions
86
Functions that are reachable but not covered
8
Reachable functions
13
Percentage of reachable functions covered
38.46%
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_core 5
requests_ntlm2.core 7

Fuzzer: fuzz_auth

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 427 99.0%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 4 0.92%
All colors 431 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
420 10 requests_ntlm2.core.get_ntlm_credentials call site: 00010 requests.sessions.Session.get
5 4 ...fuzz_auth.ServerThread.__init__ call site: 00004 requests_ntlm2.requests_ntlm2.HttpNtlmAuth.__init__
2 0 EP call site: 00000 ...fuzz_auth.ServerThread.__init__

Runtime coverage analysis

Covered functions
87
Functions that are reachable but not covered
232
Reachable functions
245
Percentage of reachable functions covered
5.31%
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.
Function name source code lines source lines hit percentage hit

Files reached

filename functions hit
/ 1
...fuzz_auth 10
requests_ntlm2.requests_ntlm2 1
requests_ntlm2.core 1
requests.sessions 78
requests.models 74
requests.cookies 29
requests.utils 72
requests._internal_utils 6
requests.structures 4
requests.hooks 2
requests.auth 8

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
requests.adapters.HTTPAdapter.send requests.adapters 7 ['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A'] 5 0 3 10 7 90 0 295 157
requests_ntlm2.requests_ntlm2.HttpNtlmAuth.response_hook requests_ntlm2.requests_ntlm2 3 ['N/A', 'N/A', 'N/A'] 5 0 1 4 5 57 0 184 140
requests.auth.HTTPDigestAuth.handle_401 requests.auth 3 ['N/A', 'N/A', 'N/A'] 4 0 7 3 4 38 0 126 102
requests_ntlm2.connection.VerifiedHTTPSConnection._tunnel requests_ntlm2.connection 1 ['N/A'] 4 0 18 10 7 50 0 163 78
requests.models.Response.iter_lines requests.models 4 ['N/A', 'N/A', 'N/A', 'N/A'] 3 0 3 4 5 12 0 44 35

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

Functions statically reachable by fuzzers
44.0%
124 / 282
Cyclomatic complexity statically reachable by fuzzers
49.0%
474 / 976

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
requests_ntlm2.requests_ntlm2.HttpNtlmAuth.retry_using_http_ntlm_auth 32 0 0.0% []
response._read_status 137 34 24.81% []
urllib3.poolmanager.PoolManager.clear 234 86 36.75% []
requests.auth.HTTPDigestAuth.build_digest_header.sha512_utf8 44 0 0.0% []
six.moves.urllib.parse.urlparse 501 250 49.90% []
requests.utils.get_netrc_auth 32 0 0.0% ['fuzz_auth']
request.method.upper 103 46 44.66% ['fuzz_auth']
requests_ntlm2.connection.VerifiedHTTPSConnection._tunnel 67 5 7.462% []
requests.adapters.HTTPAdapter.send 45 0 0.0% []
urllib3.util.retry.Retry.from_int 174 61 35.05% []
urllib3.contrib.socks.SOCKSProxyManager 87 9 10.34% []
url.strip 206 60 29.12% []
requests.models.RequestEncodingMixin._encode_files 38 0 0.0% ['fuzz_auth']
requests.models.PreparedRequest.prepare_url 39 0 0.0% ['fuzz_auth']
requests.models.PreparedRequest.prepare_body 38 0 0.0% ['fuzz_auth']
urllib3.fields.RequestField.make_multipart 93 20 21.50% ['fuzz_auth']
urllib3.filepost.encode_multipart_formdata 37 13 35.13% ['fuzz_auth']
ntlm_auth.messages.ChallengeMessage 231 66 28.57% ['fuzz_core']
d.items 189 25 13.22% []
collections.OrderedDict.pop 232 75 32.32% []
requests.sessions.SessionRedirectMixin.resolve_redirects 50 0 0.0% ['fuzz_auth']
requests.sessions.Session.send 36 0 0.0% ['fuzz_auth']

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
[] []
urllib3 [] []
requests.compat [] []
chardet [] []
http [] []
requests_ntlm2.connection [] []
requests._internal_utils ['fuzz_auth'] []
...fuzz_auth ['fuzz_auth'] []
ntlm_auth [] []
netrc [] []
requests.exceptions [] []
binascii [] []
hashlib [] []
requests.__version__ [] []
simplejson [] []
certifi [] []
re [] []
copy [] []
idna [] []
time [] []
requests.adapters [] []
requests.api [] []
select [] []
datetime [] []
urllib [] []
struct [] []
codecs [] []
collections [] []
cryptography [] []
requests.structures ['fuzz_auth'] []
requests.packages [] []
platform [] []
zipfile [] []
base64 [] []
winreg [] []
[] []
requests.status_codes [] []
requests.utils ['fuzz_auth'] []
...fuzz_core ['fuzz_core'] []
requests.sessions ['fuzz_auth'] []
logging [] []
requests_ntlm2.adapters [] []
dummy_threading [] []
calendar [] []
json [] []
requests.hooks ['fuzz_auth'] []
warnings [] []
requests.cookies ['fuzz_auth'] []
socket [] []
threading [] []
tempfile [] []
requests.auth ['fuzz_auth'] []
six [] []
requests.help [] []
requests_ntlm2.requests_ntlm2 ['fuzz_auth'] []
atheris [] []
requests_ntlm2.core ['fuzz_core', 'fuzz_auth'] []
os [] []
requests.models ['fuzz_auth'] []
requests [] []
requests_ntlm2 [] []
requests_ntlm2.dance [] []
requests.certs [] []
charset_normalizer [] []

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_core fuzzerLogFile-fuzz_core.data fuzzerLogFile-fuzz_core.data.yaml all_cov.json
fuzz_auth fuzzerLogFile-fuzz_auth.data fuzzerLogFile-fuzz_auth.data.yaml all_cov.json