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

Table of contents

Project overview: msal
High level conclusions
Reachability and coverage overview
Fuzzers overview
Project functions overview
Fuzzer details
Fuzzer: fuzz_tokencache
Call tree
Fuzz blockers
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-06-07

Project overview: msal

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
20.0%
80 / 405
Cyclomatic complexity statically reachable by fuzzers
21.0%
298 / 1406
Runtime code coverage of functions
18.0%
73 / 405

Fuzzers overview

Fuzzer Fuzzer filename Functions Reached Functions unreached Fuzzer depth Files reached Basic blocks reached Cyclomatic complexity Details
fuzz_tokencache /src/fuzz_tokencache.py 11 426 2 2 1 30 fuzz_tokencache.py
fuzz_auth /src/fuzz_auth.py 259 701 11 13 163 833 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_tokencache

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 4 30.7%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 9 69.2%
All colors 13 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
4 3 ...fuzz_tokencache.TestInput call site: 00003 ...fuzz_tokencache.build_token

Runtime coverage analysis

Covered functions
56
Functions that are reachable but not covered
10
Reachable functions
11
Percentage of reachable functions covered
9.09%
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_tokencache 10

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 436 95.4%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 21 4.59%
All colors 457 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
299 150 requests.structures.CaseInsensitiveDict.__init__ call site: 00150 requests.sessions.Session.send
104 44 requests.cookies.cookiejar_from_dict call site: 00044 requests.models.PreparedRequest.prepare
32 11 ...fuzz_auth.TestInput call site: 00011 requests.sessions.Session.get
1 454 msal.application.extract_certs call site: 00454 cert.strip

Runtime coverage analysis

Covered functions
127
Functions that are reachable but not covered
242
Reachable functions
259
Percentage of reachable functions covered
6.56%
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
msal.authority 2
msal.application 19
msal.cloudshell 1
requests.sessions 80
requests.models 76
requests.cookies 27
requests.utils 71
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
msal.application.ClientApplication.acquire_token_silent_with_error msal.application 7 ['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A'] 4 0 3 6 5 128 1 415 325
requests.adapters.HTTPAdapter.send requests.adapters 7 ['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A'] 3 0 3 10 7 90 0 295 157
requests.auth.HTTPDigestAuth.handle_401 requests.auth 3 ['N/A', 'N/A', 'N/A'] 3 0 7 3 4 38 0 126 105
msal.oauth2cli.oauth2.Client.obtain_token_by_browser msal.oauth2cli.oauth2 4 ['N/A', 'N/A', 'N/A', 'N/A'] 2 0 2 2 4 48 0 153 96
msal.application.ClientApplication.acquire_token_by_username_password msal.application 6 ['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A'] 3 0 3 3 4 73 0 231 76
msal.application.PublicClientApplication.acquire_token_interactive msal.application 13 ['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A'] 3 0 5 5 5 97 0 315 48
requests.models.Response.iter_lines requests.models 4 ['N/A', 'N/A', 'N/A', 'N/A'] 1 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
42.0%
172 / 405
Cyclomatic complexity statically reachable by fuzzers
47.0%
654 / 1406

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
msal.application.ClientApplication.__init__ 50 18 36.0% []
msal.application.ClientApplication._build_client 33 0 0.0% []
msal.application.ClientApplication._acquire_token_silent_from_cache_and_possibly_refresh_it 39 0 0.0% []
msal.application.PublicClientApplication._acquire_token_interactive_via_broker 31 0 0.0% []
e.get 37 13 35.13% []
requests.adapters.HTTPAdapter 197 64 32.48% []
rt.get 161 49 30.43% []
requests.sessions.SessionRedirectMixin.resolve_redirects 50 0 0.0% ['fuzz_auth']
requests.sessions.Session.send 36 0 0.0% ['fuzz_auth']
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']
requests.utils.get_netrc_auth 32 0 0.0% ['fuzz_auth']
collections.OrderedDict.pop 212 72 33.96% []
requests.auth.HTTPDigestAuth.build_digest_header.sha512_utf8 44 0 0.0% []
requests.adapters.HTTPAdapter.send 45 0 0.0% []
urllib3.util.retry.Retry.from_int 174 61 35.05% []
r.register_hook 232 86 37.06% []
urllib3.contrib.socks.SOCKSProxyManager 87 9 10.34% []
url.strip 206 60 29.12% []
x.encode 62 19 30.64% []
urllib3.fields.RequestField.make_multipart 93 20 21.50% ['fuzz_auth']
urllib3.filepost.encode_multipart_formdata 37 13 35.13% ['fuzz_auth']
d.items 189 25 13.22% []

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
[] []
base64 [] []
requests.status_codes [] []
simplejson [] []
urllib3 [] []
requests.hooks ['fuzz_auth'] []
pymsalruntime [] []
msal.wstrust_response [] []
msal.cloudshell ['fuzz_auth'] []
urlparse [] []
threading [] []
requests.api [] []
msal.region [] []
cryptography [] []
atheris [] []
platform [] []
webbrowser [] []
msal [] []
charset_normalizer [] []
msal.broker [] []
msal.individual_cache [] []
hashlib [] []
requests.__version__ [] []
socket [] []
requests.cookies ['fuzz_auth'] []
copy [] []
collections [] []
requests.packages [] []
subprocess [] []
urllib [] []
requests [] []
logging [] []
chardet [] []
struct [] []
http [] []
msal.oauth2cli.authcode [] []
msal.telemetry [] []
msal.oauth2cli [] []
argparse [] []
requests.compat [] []
codecs [] []
msal.authority ['fuzz_auth'] []
functools [] []
netrc [] []
heapq [] []
binascii [] []
winreg [] []
msal.oauth2cli.oauth2 [] []
...fuzz_auth ['fuzz_auth'] []
random [] []
msal.oauth2cli.http [] []
xml [] []
requests.auth ['fuzz_auth'] []
requests.certs [] []
jwt [] []
dummy_threading [] []
time [] []
requests.exceptions [] []
msal.application ['fuzz_auth'] []
tempfile [] []
certifi [] []
msal.oauth2cli.assertion [] []
requests.adapters [] []
msal.throttled_http_client [] []
requests.models ['fuzz_auth'] []
string [] []
os [] []
requests.sessions ['fuzz_auth'] []
json [] []
warnings [] []
msal.wstrust_request [] []
datetime [] []
calendar [] []
[] []
requests.utils ['fuzz_auth'] []
requests.help [] []
idna [] []
zipfile [] []
re [] []
requests._internal_utils ['fuzz_auth'] []
requests.structures ['fuzz_auth'] []
msal.oauth2cli.oidc [] []
uuid [] []
...fuzz_tokencache ['fuzz_tokencache'] []

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_tokencache fuzzerLogFile-fuzz_tokencache.data fuzzerLogFile-fuzz_tokencache.data.yaml all_cov.json
fuzz_auth fuzzerLogFile-fuzz_auth.data fuzzerLogFile-fuzz_auth.data.yaml all_cov.json