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

Fuzzer details

Fuzzer: fuzz_ntlm_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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is
Color Runtime hitcount Callsite count Percentage
red 0 100 68.0%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 47 31.9%
All colors 147 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
51 22 ntlm_auth.compute_hash._lmowfv1 call site: 00022 ntlm_auth.des.DES.encrypt
14 87 ...fuzz_ntlm_auth.fuzz_compute_response call site: 00087 ntlm_auth.compute_response.ComputeResponse._calc_resp
9 12 ntlm_auth.compute_hash._lmowfv1 call site: 00012 .len
7 116 ...fuzz_ntlm_auth.fuzz_compute_response call site: 00116 ntlm_auth.compute_hash._ntowfv2
5 103 ...fuzz_ntlm_auth.fuzz_compute_response call site: 00103 ntlm_auth.compute_response.ComputeResponse._calc_resp
3 78 ...fuzz_ntlm_auth.fuzz_hash call site: 00078 re.match
3 137 ...fuzz_ntlm_auth.fuzz_compute_keys call site: 00137 fdp.ConsumeBytes
3 143 ...fuzz_ntlm_auth.fuzz_compute_keys call site: 00143 ntlm_auth.compute_keys._get_seal_key_ntlm2
2 111 ...fuzz_ntlm_auth.fuzz_compute_response call site: 00111 ntlm_auth.compute_hash._lmowfv1
1 7 ntlm_auth.compute_hash._lmowfv1 call site: 00007 password.upper
1 132 ntlm_auth.compute_keys._get_exchange_key_ntlm_v1 call site: 00132 ntlm_auth.des.DES.encrypt
1 135 ntlm_auth.compute_keys._get_exchange_key_ntlm_v1 call site: 00135 ntlm_auth.des.DES.encrypt

Runtime coverage analysis

Covered functions
Functions that are reachable but not covered
Reachable functions
Percentage of reachable functions covered
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_ntlm_auth 15
ntlm_auth.compute_hash 13
ntlm_auth.des 21
ntlm_auth.compute_response 11
ntlm_auth.compute_keys 7