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

Fuzzer details

Fuzzer: xml_parsebuffer_fuzzer_UTF-16LE

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 27 15.0%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 1 0.55%
lawngreen 50+ 152 84.4%
All colors 180 100

Fuzz blockers

The followings are the branches where fuzzer fails to bypass.

Unique non-covered Complexity Unique Reachable Complexities Unique Reachable Functions All non-covered Complexity All Reachable Complexity Function Name Function Callsite Blocked Branch
489 489 1 :

['entityValueInitProcessor']

489 489 externalParEntInitProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:4493
272 286 2 :

['accountingReportStats', 'accountingReportDiff']

272 286 accountingDiffTolerated call site: 00000 /src/expat/expat/lib/xmlparse.c:7913
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3078
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3139
50 50 1 :

['generate_hash_secret_salt']

50 310 startParsing call site: 00061 /src/expat/expat/lib/xmlparse.c:1044
8 8 2 :

['__errno_location', 'strtoul']

8 8 getDebugLevel call site: 00021 /src/expat/expat/lib/xmlparse.c:8526
6 6 1 :

['reportDefault']

6 6 epilogProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:5764
6 6 1 :

['reportDefault']

6 6 doIgnoreSection call site: 00000 /src/expat/expat/lib/xmlparse.c:4273
6 6 1 :

['reportDefault']

6 6 reportProcessingInstruction call site: 00000 /src/expat/expat/lib/xmlparse.c:6423
6 6 1 :

['reportDefault']

6 6 reportComment call site: 00000 /src/expat/expat/lib/xmlparse.c:6448
2 2 1 :

['XmlSizeOfUnknownEncoding']

2 2 handleUnknownEncoding call site: 00000 /src/expat/expat/lib/xmlparse.c:4438
0 1493 1 :

['doProlog']

0 1506 processInternalEntity call site: 00000 /src/expat/expat/lib/xmlparse.c:5850

Runtime coverage analysis

Covered functions
275
Functions that are reachable but not covered
16
Reachable functions
84
Percentage of reachable functions covered
80.95%
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
fuzz/xml_parsebuffer_fuzzer.c 4
lib/xmlparse.c 54
lib/xmlrole.c 2
lib/xmltok_ns.c 3
lib/xmltok.c 2
lib/siphash.h 6

Fuzzer: xml_parsebuffer_fuzzer_UTF-16BE

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 27 15.0%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 1 0.55%
lawngreen 50+ 152 84.4%
All colors 180 100

Fuzz blockers

The followings are the branches where fuzzer fails to bypass.

Unique non-covered Complexity Unique Reachable Complexities Unique Reachable Functions All non-covered Complexity All Reachable Complexity Function Name Function Callsite Blocked Branch
489 489 1 :

['entityValueInitProcessor']

489 489 externalParEntInitProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:4493
272 286 2 :

['accountingReportStats', 'accountingReportDiff']

272 286 accountingDiffTolerated call site: 00000 /src/expat/expat/lib/xmlparse.c:7913
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3078
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3139
50 50 1 :

['generate_hash_secret_salt']

50 310 startParsing call site: 00061 /src/expat/expat/lib/xmlparse.c:1044
8 8 2 :

['__errno_location', 'strtoul']

8 8 getDebugLevel call site: 00021 /src/expat/expat/lib/xmlparse.c:8526
6 6 1 :

['reportDefault']

6 6 epilogProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:5764
6 6 1 :

['reportDefault']

6 6 doIgnoreSection call site: 00000 /src/expat/expat/lib/xmlparse.c:4273
6 6 1 :

['reportDefault']

6 6 reportProcessingInstruction call site: 00000 /src/expat/expat/lib/xmlparse.c:6423
6 6 1 :

['reportDefault']

6 6 reportComment call site: 00000 /src/expat/expat/lib/xmlparse.c:6448
2 2 1 :

['XmlSizeOfUnknownEncoding']

2 2 handleUnknownEncoding call site: 00000 /src/expat/expat/lib/xmlparse.c:4438
0 1493 1 :

['doProlog']

0 1506 processInternalEntity call site: 00000 /src/expat/expat/lib/xmlparse.c:5850

Runtime coverage analysis

Covered functions
275
Functions that are reachable but not covered
16
Reachable functions
84
Percentage of reachable functions covered
80.95%
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
fuzz/xml_parsebuffer_fuzzer.c 4
lib/xmlparse.c 54
lib/xmlrole.c 2
lib/xmltok_ns.c 3
lib/xmltok.c 2
lib/siphash.h 6

Fuzzer: xml_parse_fuzzer_UTF-16

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 28 15.4%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 1 0.55%
lawngreen 50+ 152 83.9%
All colors 181 100

Fuzz blockers

The followings are the branches where fuzzer fails to bypass.

Unique non-covered Complexity Unique Reachable Complexities Unique Reachable Functions All non-covered Complexity All Reachable Complexity Function Name Function Callsite Blocked Branch
489 489 1 :

['entityValueInitProcessor']

489 489 externalParEntInitProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:4493
272 286 2 :

['accountingReportStats', 'accountingReportDiff']

272 286 accountingDiffTolerated call site: 00000 /src/expat/expat/lib/xmlparse.c:7913
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3078
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3139
50 50 1 :

['generate_hash_secret_salt']

50 310 startParsing call site: 00059 /src/expat/expat/lib/xmlparse.c:1044
8 8 2 :

['__errno_location', 'strtoul']

8 8 getDebugLevel call site: 00021 /src/expat/expat/lib/xmlparse.c:8526
6 6 1 :

['reportDefault']

6 6 epilogProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:5764
6 6 1 :

['reportDefault']

6 6 doIgnoreSection call site: 00000 /src/expat/expat/lib/xmlparse.c:4273
6 6 1 :

['reportDefault']

6 6 reportProcessingInstruction call site: 00000 /src/expat/expat/lib/xmlparse.c:6423
6 6 1 :

['reportDefault']

6 6 reportComment call site: 00000 /src/expat/expat/lib/xmlparse.c:6448
2 2 1 :

['XmlSizeOfUnknownEncoding']

2 2 handleUnknownEncoding call site: 00000 /src/expat/expat/lib/xmlparse.c:4438
0 1493 1 :

['doProlog']

0 1506 processInternalEntity call site: 00000 /src/expat/expat/lib/xmlparse.c:5850

Runtime coverage analysis

Covered functions
276
Functions that are reachable but not covered
16
Reachable functions
85
Percentage of reachable functions covered
81.18%
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
fuzz/xml_parse_fuzzer.c 4
lib/xmlparse.c 55
lib/xmlrole.c 2
lib/xmltok_ns.c 3
lib/xmltok.c 2
lib/siphash.h 6

Fuzzer: xml_parsebuffer_fuzzer_US-ASCII

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 27 15.0%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 1 0.55%
lawngreen 50+ 152 84.4%
All colors 180 100

Fuzz blockers

The followings are the branches where fuzzer fails to bypass.

Unique non-covered Complexity Unique Reachable Complexities Unique Reachable Functions All non-covered Complexity All Reachable Complexity Function Name Function Callsite Blocked Branch
489 489 1 :

['entityValueInitProcessor']

489 489 externalParEntInitProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:4493
272 286 2 :

['accountingReportStats', 'accountingReportDiff']

272 286 accountingDiffTolerated call site: 00000 /src/expat/expat/lib/xmlparse.c:7913
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3078
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3139
50 50 1 :

['generate_hash_secret_salt']

50 310 startParsing call site: 00061 /src/expat/expat/lib/xmlparse.c:1044
8 8 2 :

['__errno_location', 'strtoul']

8 8 getDebugLevel call site: 00021 /src/expat/expat/lib/xmlparse.c:8526
6 6 1 :

['reportDefault']

6 6 epilogProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:5764
6 6 1 :

['reportDefault']

6 6 doIgnoreSection call site: 00000 /src/expat/expat/lib/xmlparse.c:4273
6 6 1 :

['reportDefault']

6 6 reportProcessingInstruction call site: 00000 /src/expat/expat/lib/xmlparse.c:6423
6 6 1 :

['reportDefault']

6 6 reportComment call site: 00000 /src/expat/expat/lib/xmlparse.c:6448
2 2 1 :

['XmlSizeOfUnknownEncoding']

2 2 handleUnknownEncoding call site: 00000 /src/expat/expat/lib/xmlparse.c:4438
0 1493 1 :

['doProlog']

0 1506 processInternalEntity call site: 00000 /src/expat/expat/lib/xmlparse.c:5850

Runtime coverage analysis

Covered functions
273
Functions that are reachable but not covered
16
Reachable functions
84
Percentage of reachable functions covered
80.95%
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
fuzz/xml_parsebuffer_fuzzer.c 4
lib/xmlparse.c 54
lib/xmlrole.c 2
lib/xmltok_ns.c 3
lib/xmltok.c 2
lib/siphash.h 6

Fuzzer: xml_parse_fuzzer_UTF-16BE

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 28 15.4%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 1 0.55%
lawngreen 50+ 152 83.9%
All colors 181 100

Fuzz blockers

The followings are the branches where fuzzer fails to bypass.

Unique non-covered Complexity Unique Reachable Complexities Unique Reachable Functions All non-covered Complexity All Reachable Complexity Function Name Function Callsite Blocked Branch
489 489 1 :

['entityValueInitProcessor']

489 489 externalParEntInitProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:4493
272 286 2 :

['accountingReportStats', 'accountingReportDiff']

272 286 accountingDiffTolerated call site: 00000 /src/expat/expat/lib/xmlparse.c:7913
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3078
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3139
50 50 1 :

['generate_hash_secret_salt']

50 310 startParsing call site: 00059 /src/expat/expat/lib/xmlparse.c:1044
8 8 2 :

['__errno_location', 'strtoul']

8 8 getDebugLevel call site: 00021 /src/expat/expat/lib/xmlparse.c:8526
6 6 1 :

['reportDefault']

6 6 epilogProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:5764
6 6 1 :

['reportDefault']

6 6 doIgnoreSection call site: 00000 /src/expat/expat/lib/xmlparse.c:4273
6 6 1 :

['reportDefault']

6 6 reportProcessingInstruction call site: 00000 /src/expat/expat/lib/xmlparse.c:6423
6 6 1 :

['reportDefault']

6 6 reportComment call site: 00000 /src/expat/expat/lib/xmlparse.c:6448
2 2 1 :

['XmlSizeOfUnknownEncoding']

2 2 handleUnknownEncoding call site: 00000 /src/expat/expat/lib/xmlparse.c:4438
0 1493 1 :

['doProlog']

0 1506 processInternalEntity call site: 00000 /src/expat/expat/lib/xmlparse.c:5850

Runtime coverage analysis

Covered functions
276
Functions that are reachable but not covered
16
Reachable functions
85
Percentage of reachable functions covered
81.18%
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
fuzz/xml_parse_fuzzer.c 4
lib/xmlparse.c 55
lib/xmlrole.c 2
lib/xmltok_ns.c 3
lib/xmltok.c 2
lib/siphash.h 6

Fuzzer: xml_parse_fuzzer_US-ASCII

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 28 15.4%
gold [1:9] 0 0.0%
yellow [10:29] 1 0.55%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 152 83.9%
All colors 181 100

Fuzz blockers

The followings are the branches where fuzzer fails to bypass.

Unique non-covered Complexity Unique Reachable Complexities Unique Reachable Functions All non-covered Complexity All Reachable Complexity Function Name Function Callsite Blocked Branch
489 489 1 :

['entityValueInitProcessor']

489 489 externalParEntInitProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:4493
272 286 2 :

['accountingReportStats', 'accountingReportDiff']

272 286 accountingDiffTolerated call site: 00000 /src/expat/expat/lib/xmlparse.c:7913
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3078
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3139
50 50 1 :

['generate_hash_secret_salt']

50 310 startParsing call site: 00059 /src/expat/expat/lib/xmlparse.c:1044
8 8 2 :

['__errno_location', 'strtoul']

8 8 getDebugLevel call site: 00021 /src/expat/expat/lib/xmlparse.c:8526
6 6 1 :

['reportDefault']

6 6 epilogProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:5764
6 6 1 :

['reportDefault']

6 6 doIgnoreSection call site: 00000 /src/expat/expat/lib/xmlparse.c:4273
6 6 1 :

['reportDefault']

6 6 reportProcessingInstruction call site: 00000 /src/expat/expat/lib/xmlparse.c:6423
6 6 1 :

['reportDefault']

6 6 reportComment call site: 00000 /src/expat/expat/lib/xmlparse.c:6448
2 2 1 :

['XmlSizeOfUnknownEncoding']

2 2 handleUnknownEncoding call site: 00000 /src/expat/expat/lib/xmlparse.c:4438
0 1493 1 :

['doProlog']

0 1506 processInternalEntity call site: 00000 /src/expat/expat/lib/xmlparse.c:5850

Runtime coverage analysis

Covered functions
274
Functions that are reachable but not covered
16
Reachable functions
85
Percentage of reachable functions covered
81.18%
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
fuzz/xml_parse_fuzzer.c 4
lib/xmlparse.c 55
lib/xmlrole.c 2
lib/xmltok_ns.c 3
lib/xmltok.c 2
lib/siphash.h 6

Fuzzer: xml_parse_fuzzer_UTF-8

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 28 15.4%
gold [1:9] 0 0.0%
yellow [10:29] 1 0.55%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 152 83.9%
All colors 181 100

Fuzz blockers

The followings are the branches where fuzzer fails to bypass.

Unique non-covered Complexity Unique Reachable Complexities Unique Reachable Functions All non-covered Complexity All Reachable Complexity Function Name Function Callsite Blocked Branch
489 489 1 :

['entityValueInitProcessor']

489 489 externalParEntInitProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:4493
272 286 2 :

['accountingReportStats', 'accountingReportDiff']

272 286 accountingDiffTolerated call site: 00000 /src/expat/expat/lib/xmlparse.c:7913
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3078
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3139
50 50 1 :

['generate_hash_secret_salt']

50 310 startParsing call site: 00059 /src/expat/expat/lib/xmlparse.c:1044
8 8 2 :

['__errno_location', 'strtoul']

8 8 getDebugLevel call site: 00021 /src/expat/expat/lib/xmlparse.c:8526
6 6 1 :

['reportDefault']

6 6 epilogProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:5764
6 6 1 :

['reportDefault']

6 6 doIgnoreSection call site: 00000 /src/expat/expat/lib/xmlparse.c:4273
6 6 1 :

['reportDefault']

6 6 reportProcessingInstruction call site: 00000 /src/expat/expat/lib/xmlparse.c:6423
6 6 1 :

['reportDefault']

6 6 reportComment call site: 00000 /src/expat/expat/lib/xmlparse.c:6448
2 2 1 :

['XmlSizeOfUnknownEncoding']

2 2 handleUnknownEncoding call site: 00000 /src/expat/expat/lib/xmlparse.c:4438
0 1493 1 :

['doProlog']

0 1506 processInternalEntity call site: 00000 /src/expat/expat/lib/xmlparse.c:5850

Runtime coverage analysis

Covered functions
274
Functions that are reachable but not covered
16
Reachable functions
85
Percentage of reachable functions covered
81.18%
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
fuzz/xml_parse_fuzzer.c 4
lib/xmlparse.c 55
lib/xmlrole.c 2
lib/xmltok_ns.c 3
lib/xmltok.c 2
lib/siphash.h 6

Fuzzer: xml_parsebuffer_fuzzer_ISO-8859-1

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 27 15.0%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 153 85.0%
All colors 180 100

Fuzz blockers

The followings are the branches where fuzzer fails to bypass.

Unique non-covered Complexity Unique Reachable Complexities Unique Reachable Functions All non-covered Complexity All Reachable Complexity Function Name Function Callsite Blocked Branch
489 489 1 :

['entityValueInitProcessor']

489 489 externalParEntInitProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:4493
272 286 2 :

['accountingReportStats', 'accountingReportDiff']

272 286 accountingDiffTolerated call site: 00000 /src/expat/expat/lib/xmlparse.c:7913
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3078
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3139
50 50 1 :

['generate_hash_secret_salt']

50 310 startParsing call site: 00061 /src/expat/expat/lib/xmlparse.c:1044
8 8 2 :

['__errno_location', 'strtoul']

8 8 getDebugLevel call site: 00021 /src/expat/expat/lib/xmlparse.c:8526
6 6 1 :

['reportDefault']

6 6 epilogProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:5764
6 6 1 :

['reportDefault']

6 6 doIgnoreSection call site: 00000 /src/expat/expat/lib/xmlparse.c:4273
6 6 1 :

['reportDefault']

6 6 reportProcessingInstruction call site: 00000 /src/expat/expat/lib/xmlparse.c:6423
6 6 1 :

['reportDefault']

6 6 reportComment call site: 00000 /src/expat/expat/lib/xmlparse.c:6448
2 2 1 :

['XmlSizeOfUnknownEncoding']

2 2 handleUnknownEncoding call site: 00000 /src/expat/expat/lib/xmlparse.c:4438
0 1493 1 :

['doProlog']

0 1506 processInternalEntity call site: 00000 /src/expat/expat/lib/xmlparse.c:5850

Runtime coverage analysis

Covered functions
275
Functions that are reachable but not covered
16
Reachable functions
84
Percentage of reachable functions covered
80.95%
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
fuzz/xml_parsebuffer_fuzzer.c 4
lib/xmlparse.c 54
lib/xmlrole.c 2
lib/xmltok_ns.c 3
lib/xmltok.c 2
lib/siphash.h 6

Fuzzer: xml_parsebuffer_fuzzer_UTF-16

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 27 15.0%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 153 85.0%
All colors 180 100

Fuzz blockers

The followings are the branches where fuzzer fails to bypass.

Unique non-covered Complexity Unique Reachable Complexities Unique Reachable Functions All non-covered Complexity All Reachable Complexity Function Name Function Callsite Blocked Branch
489 489 1 :

['entityValueInitProcessor']

489 489 externalParEntInitProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:4493
272 286 2 :

['accountingReportStats', 'accountingReportDiff']

272 286 accountingDiffTolerated call site: 00000 /src/expat/expat/lib/xmlparse.c:7913
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3078
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3139
50 50 1 :

['generate_hash_secret_salt']

50 310 startParsing call site: 00061 /src/expat/expat/lib/xmlparse.c:1044
8 8 2 :

['__errno_location', 'strtoul']

8 8 getDebugLevel call site: 00021 /src/expat/expat/lib/xmlparse.c:8526
6 6 1 :

['reportDefault']

6 6 epilogProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:5764
6 6 1 :

['reportDefault']

6 6 doIgnoreSection call site: 00000 /src/expat/expat/lib/xmlparse.c:4273
6 6 1 :

['reportDefault']

6 6 reportProcessingInstruction call site: 00000 /src/expat/expat/lib/xmlparse.c:6423
6 6 1 :

['reportDefault']

6 6 reportComment call site: 00000 /src/expat/expat/lib/xmlparse.c:6448
2 2 1 :

['XmlSizeOfUnknownEncoding']

2 2 handleUnknownEncoding call site: 00000 /src/expat/expat/lib/xmlparse.c:4438
0 1493 1 :

['doProlog']

0 1506 processInternalEntity call site: 00000 /src/expat/expat/lib/xmlparse.c:5850

Runtime coverage analysis

Covered functions
274
Functions that are reachable but not covered
16
Reachable functions
84
Percentage of reachable functions covered
80.95%
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
fuzz/xml_parsebuffer_fuzzer.c 4
lib/xmlparse.c 54
lib/xmlrole.c 2
lib/xmltok_ns.c 3
lib/xmltok.c 2
lib/siphash.h 6

Fuzzer: xml_parse_fuzzer_ISO-8859-1

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 28 15.4%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 1 0.55%
lawngreen 50+ 152 83.9%
All colors 181 100

Fuzz blockers

The followings are the branches where fuzzer fails to bypass.

Unique non-covered Complexity Unique Reachable Complexities Unique Reachable Functions All non-covered Complexity All Reachable Complexity Function Name Function Callsite Blocked Branch
489 489 1 :

['entityValueInitProcessor']

489 489 externalParEntInitProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:4493
272 286 2 :

['accountingReportStats', 'accountingReportDiff']

272 286 accountingDiffTolerated call site: 00000 /src/expat/expat/lib/xmlparse.c:7913
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3078
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3139
50 50 1 :

['generate_hash_secret_salt']

50 310 startParsing call site: 00059 /src/expat/expat/lib/xmlparse.c:1044
8 8 2 :

['__errno_location', 'strtoul']

8 8 getDebugLevel call site: 00021 /src/expat/expat/lib/xmlparse.c:8526
6 6 1 :

['reportDefault']

6 6 epilogProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:5764
6 6 1 :

['reportDefault']

6 6 doIgnoreSection call site: 00000 /src/expat/expat/lib/xmlparse.c:4273
6 6 1 :

['reportDefault']

6 6 reportProcessingInstruction call site: 00000 /src/expat/expat/lib/xmlparse.c:6423
6 6 1 :

['reportDefault']

6 6 reportComment call site: 00000 /src/expat/expat/lib/xmlparse.c:6448
2 2 1 :

['XmlSizeOfUnknownEncoding']

2 2 handleUnknownEncoding call site: 00000 /src/expat/expat/lib/xmlparse.c:4438
0 1493 1 :

['doProlog']

0 1506 processInternalEntity call site: 00000 /src/expat/expat/lib/xmlparse.c:5850

Runtime coverage analysis

Covered functions
276
Functions that are reachable but not covered
16
Reachable functions
85
Percentage of reachable functions covered
81.18%
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
fuzz/xml_parse_fuzzer.c 4
lib/xmlparse.c 55
lib/xmlrole.c 2
lib/xmltok_ns.c 3
lib/xmltok.c 2
lib/siphash.h 6

Fuzzer: xml_parsebuffer_fuzzer_UTF-8

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 27 15.0%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 1 0.55%
lawngreen 50+ 152 84.4%
All colors 180 100

Fuzz blockers

The followings are the branches where fuzzer fails to bypass.

Unique non-covered Complexity Unique Reachable Complexities Unique Reachable Functions All non-covered Complexity All Reachable Complexity Function Name Function Callsite Blocked Branch
489 489 1 :

['entityValueInitProcessor']

489 489 externalParEntInitProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:4493
272 286 2 :

['accountingReportStats', 'accountingReportDiff']

272 286 accountingDiffTolerated call site: 00000 /src/expat/expat/lib/xmlparse.c:7913
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3078
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3139
50 50 1 :

['generate_hash_secret_salt']

50 310 startParsing call site: 00061 /src/expat/expat/lib/xmlparse.c:1044
8 8 2 :

['__errno_location', 'strtoul']

8 8 getDebugLevel call site: 00021 /src/expat/expat/lib/xmlparse.c:8526
6 6 1 :

['reportDefault']

6 6 epilogProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:5764
6 6 1 :

['reportDefault']

6 6 doIgnoreSection call site: 00000 /src/expat/expat/lib/xmlparse.c:4273
6 6 1 :

['reportDefault']

6 6 reportProcessingInstruction call site: 00000 /src/expat/expat/lib/xmlparse.c:6423
6 6 1 :

['reportDefault']

6 6 reportComment call site: 00000 /src/expat/expat/lib/xmlparse.c:6448
2 2 1 :

['XmlSizeOfUnknownEncoding']

2 2 handleUnknownEncoding call site: 00000 /src/expat/expat/lib/xmlparse.c:4438
0 1493 1 :

['doProlog']

0 1506 processInternalEntity call site: 00000 /src/expat/expat/lib/xmlparse.c:5850

Runtime coverage analysis

Covered functions
273
Functions that are reachable but not covered
16
Reachable functions
84
Percentage of reachable functions covered
80.95%
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
fuzz/xml_parsebuffer_fuzzer.c 4
lib/xmlparse.c 54
lib/xmlrole.c 2
lib/xmltok_ns.c 3
lib/xmltok.c 2
lib/siphash.h 6

Fuzzer: xml_parse_fuzzer_UTF-16LE

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 28 15.4%
gold [1:9] 0 0.0%
yellow [10:29] 1 0.55%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 152 83.9%
All colors 181 100

Fuzz blockers

The followings are the branches where fuzzer fails to bypass.

Unique non-covered Complexity Unique Reachable Complexities Unique Reachable Functions All non-covered Complexity All Reachable Complexity Function Name Function Callsite Blocked Branch
489 489 1 :

['entityValueInitProcessor']

489 489 externalParEntInitProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:4493
272 286 2 :

['accountingReportStats', 'accountingReportDiff']

272 286 accountingDiffTolerated call site: 00000 /src/expat/expat/lib/xmlparse.c:7913
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3078
162 4090 15 :

['memcmp', 'poolClear', 'reportDefault', 'lookup', 'freeBindings', 'doCdataSection', 'reportProcessingInstruction', 'XmlUtf8Encode', 'reportComment', 'poolStoreString', 'accountingOnAbort', 'getContext', 'processInternalEntity', 'storeAtts', 'accountingDiffTolerated']

162 4804 doContent call site: 00000 /src/expat/expat/lib/xmlparse.c:3139
50 50 1 :

['generate_hash_secret_salt']

50 310 startParsing call site: 00059 /src/expat/expat/lib/xmlparse.c:1044
8 8 2 :

['__errno_location', 'strtoul']

8 8 getDebugLevel call site: 00021 /src/expat/expat/lib/xmlparse.c:8526
6 6 1 :

['reportDefault']

6 6 epilogProcessor call site: 00000 /src/expat/expat/lib/xmlparse.c:5764
6 6 1 :

['reportDefault']

6 6 doIgnoreSection call site: 00000 /src/expat/expat/lib/xmlparse.c:4273
6 6 1 :

['reportDefault']

6 6 reportProcessingInstruction call site: 00000 /src/expat/expat/lib/xmlparse.c:6423
6 6 1 :

['reportDefault']

6 6 reportComment call site: 00000 /src/expat/expat/lib/xmlparse.c:6448
2 2 1 :

['XmlSizeOfUnknownEncoding']

2 2 handleUnknownEncoding call site: 00000 /src/expat/expat/lib/xmlparse.c:4438
0 1493 1 :

['doProlog']

0 1506 processInternalEntity call site: 00000 /src/expat/expat/lib/xmlparse.c:5850

Runtime coverage analysis

Covered functions
276
Functions that are reachable but not covered
16
Reachable functions
85
Percentage of reachable functions covered
81.18%
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
fuzz/xml_parse_fuzzer.c 4
lib/xmlparse.c 55
lib/xmlrole.c 2
lib/xmltok_ns.c 3
lib/xmltok.c 2
lib/siphash.h 6

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
doProlog /src/expat/expat/lib/xmlparse.c 10 ['N/A', 'N/A', 'N/A', 'N/A', 'int', 'N/A', 'N/A', 'char', 'char', 'int'] 8 0 4535 627 204 63 15 1493 1258
normal_contentTok /src/expat/expat/lib/xmltok_impl.c 4 ['N/A', 'N/A', 'N/A', 'N/A'] 3 0 571 86 24 10 0 241 241
big2_contentTok /src/expat/expat/lib/xmltok_impl.c 4 ['N/A', 'N/A', 'N/A', 'N/A'] 6 0 629 97 27 11 0 188 188
little2_contentTok /src/expat/expat/lib/xmltok_impl.c 4 ['N/A', 'N/A', 'N/A', 'N/A'] 6 0 626 97 27 11 0 188 170
normal_prologTok /src/expat/expat/lib/xmltok_impl.c 4 ['N/A', 'N/A', 'N/A', 'N/A'] 2 0 1335 206 40 7 0 155 91
XmlParseXmlDeclNS /src/expat/expat/lib/xmltok_ns.c 10 ['int', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A'] 3 0 52 3 2 7 0 84 72
big2_prologTok /src/expat/expat/lib/xmltok_impl.c 4 ['N/A', 'N/A', 'N/A', 'N/A'] 3 0 1299 194 33 8 0 130 70
little2_prologTok /src/expat/expat/lib/xmltok_impl.c 4 ['N/A', 'N/A', 'N/A', 'N/A'] 3 0 1293 194 33 8 0 130 70

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

Functions statically reachable by fuzzers
46.0%
170 / 366
Cyclomatic complexity statically reachable by fuzzers
68.0%
2569 / 3789

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

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.

fuzz/xml_parsebuffer_fuzzer.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag


Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['XML_ParseBuffer', 'getDebugLevel', 'parserInit', 'LLVMFuzzerTestOneInput', 'dtdCopy', 'copyEntityTable', 'XML_ExternalEntityParserCreate']

fuzz/xml_parsebuffer_fuzzer.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag


Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['XML_ParseBuffer', 'getDebugLevel', 'parserInit', 'LLVMFuzzerTestOneInput', 'dtdCopy', 'copyEntityTable', 'XML_ExternalEntityParserCreate']

fuzz/xml_parse_fuzzer.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag


Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['XML_Parse', 'getDebugLevel', 'parserInit', 'LLVMFuzzerTestOneInput', 'dtdCopy', 'copyEntityTable', 'XML_ExternalEntityParserCreate']

fuzz/xml_parsebuffer_fuzzer.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag


Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['XML_ParseBuffer', 'getDebugLevel', 'parserInit', 'LLVMFuzzerTestOneInput', 'dtdCopy', 'copyEntityTable', 'XML_ExternalEntityParserCreate']

fuzz/xml_parse_fuzzer.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag


Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['XML_Parse', 'getDebugLevel', 'parserInit', 'LLVMFuzzerTestOneInput', 'dtdCopy', 'copyEntityTable', 'XML_ExternalEntityParserCreate']

fuzz/xml_parse_fuzzer.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag


Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['XML_Parse', 'getDebugLevel', 'parserInit', 'LLVMFuzzerTestOneInput', 'dtdCopy', 'copyEntityTable', 'XML_ExternalEntityParserCreate']

fuzz/xml_parse_fuzzer.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag


Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['XML_Parse', 'getDebugLevel', 'parserInit', 'LLVMFuzzerTestOneInput', 'dtdCopy', 'copyEntityTable', 'XML_ExternalEntityParserCreate']

fuzz/xml_parsebuffer_fuzzer.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag


Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['XML_ParseBuffer', 'getDebugLevel', 'parserInit', 'LLVMFuzzerTestOneInput', 'dtdCopy', 'copyEntityTable', 'XML_ExternalEntityParserCreate']

fuzz/xml_parsebuffer_fuzzer.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag


Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['XML_ParseBuffer', 'getDebugLevel', 'parserInit', 'LLVMFuzzerTestOneInput', 'dtdCopy', 'copyEntityTable', 'XML_ExternalEntityParserCreate']

fuzz/xml_parse_fuzzer.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag


Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['XML_Parse', 'getDebugLevel', 'parserInit', 'LLVMFuzzerTestOneInput', 'dtdCopy', 'copyEntityTable', 'XML_ExternalEntityParserCreate']

fuzz/xml_parsebuffer_fuzzer.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag


Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['XML_ParseBuffer', 'getDebugLevel', 'parserInit', 'LLVMFuzzerTestOneInput', 'dtdCopy', 'copyEntityTable', 'XML_ExternalEntityParserCreate']

fuzz/xml_parse_fuzzer.c

Dictionary

Use this with the libFuzzer -dict=DICT.file flag


Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['XML_Parse', 'getDebugLevel', 'parserInit', 'LLVMFuzzerTestOneInput', 'dtdCopy', 'copyEntityTable', 'XML_ExternalEntityParserCreate']

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/expat/expat/lib/siphash.h ['xml_parsebuffer_fuzzer_UTF-16LE', 'xml_parsebuffer_fuzzer_UTF-16BE', 'xml_parse_fuzzer_UTF-16', 'xml_parsebuffer_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-16BE', 'xml_parse_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-8', 'xml_parsebuffer_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-16', 'xml_parse_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-8', 'xml_parse_fuzzer_UTF-16LE'] ['xml_parsebuffer_fuzzer_UTF-16LE', 'xml_parsebuffer_fuzzer_UTF-16BE', 'xml_parse_fuzzer_UTF-16', 'xml_parsebuffer_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-16BE', 'xml_parse_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-8', 'xml_parsebuffer_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-16', 'xml_parse_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-8', 'xml_parse_fuzzer_UTF-16LE']
[] []
/src/expat/expat/fuzz/xml_parse_fuzzer.c ['xml_parse_fuzzer_UTF-16', 'xml_parse_fuzzer_UTF-16BE', 'xml_parse_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-8', 'xml_parse_fuzzer_ISO-8859-1', 'xml_parse_fuzzer_UTF-16LE'] ['xml_parse_fuzzer_UTF-16', 'xml_parse_fuzzer_UTF-16BE', 'xml_parse_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-8', 'xml_parse_fuzzer_ISO-8859-1', 'xml_parse_fuzzer_UTF-16LE']
/src/expat/expat/lib/xmltok.c ['xml_parsebuffer_fuzzer_UTF-16LE', 'xml_parsebuffer_fuzzer_UTF-16BE', 'xml_parse_fuzzer_UTF-16', 'xml_parsebuffer_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-16BE', 'xml_parse_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-8', 'xml_parsebuffer_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-16', 'xml_parse_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-8', 'xml_parse_fuzzer_UTF-16LE'] ['xml_parsebuffer_fuzzer_UTF-16LE', 'xml_parsebuffer_fuzzer_UTF-16BE', 'xml_parse_fuzzer_UTF-16', 'xml_parsebuffer_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-16BE', 'xml_parse_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-8', 'xml_parsebuffer_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-16', 'xml_parse_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-8', 'xml_parse_fuzzer_UTF-16LE']
/src/expat/expat/lib/xmlrole.c ['xml_parsebuffer_fuzzer_UTF-16LE', 'xml_parsebuffer_fuzzer_UTF-16BE', 'xml_parse_fuzzer_UTF-16', 'xml_parsebuffer_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-16BE', 'xml_parse_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-8', 'xml_parsebuffer_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-16', 'xml_parse_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-8', 'xml_parse_fuzzer_UTF-16LE'] ['xml_parsebuffer_fuzzer_UTF-16LE', 'xml_parsebuffer_fuzzer_UTF-16BE', 'xml_parse_fuzzer_UTF-16', 'xml_parsebuffer_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-16BE', 'xml_parse_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-8', 'xml_parsebuffer_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-16', 'xml_parse_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-8', 'xml_parse_fuzzer_UTF-16LE']
/src/expat/expat/fuzz/xml_parsebuffer_fuzzer.c ['xml_parsebuffer_fuzzer_UTF-16LE', 'xml_parsebuffer_fuzzer_UTF-16BE', 'xml_parsebuffer_fuzzer_US-ASCII', 'xml_parsebuffer_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-16', 'xml_parsebuffer_fuzzer_UTF-8'] ['xml_parsebuffer_fuzzer_UTF-16LE', 'xml_parsebuffer_fuzzer_UTF-16BE', 'xml_parsebuffer_fuzzer_US-ASCII', 'xml_parsebuffer_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-16', 'xml_parsebuffer_fuzzer_UTF-8']
/src/expat/expat/lib/xmltok_ns.c ['xml_parsebuffer_fuzzer_UTF-16LE', 'xml_parsebuffer_fuzzer_UTF-16BE', 'xml_parse_fuzzer_UTF-16', 'xml_parsebuffer_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-16BE', 'xml_parse_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-8', 'xml_parsebuffer_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-16', 'xml_parse_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-8', 'xml_parse_fuzzer_UTF-16LE'] ['xml_parsebuffer_fuzzer_UTF-16LE', 'xml_parsebuffer_fuzzer_UTF-16BE', 'xml_parse_fuzzer_UTF-16', 'xml_parsebuffer_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-16BE', 'xml_parse_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-8', 'xml_parsebuffer_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-16', 'xml_parse_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-8', 'xml_parse_fuzzer_UTF-16LE']
/src/expat/expat/lib/xmltok_impl.c [] []
/src/expat/expat/lib/xmlparse.c ['xml_parsebuffer_fuzzer_UTF-16LE', 'xml_parsebuffer_fuzzer_UTF-16BE', 'xml_parse_fuzzer_UTF-16', 'xml_parsebuffer_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-16BE', 'xml_parse_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-8', 'xml_parsebuffer_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-16', 'xml_parse_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-8', 'xml_parse_fuzzer_UTF-16LE'] ['xml_parsebuffer_fuzzer_UTF-16LE', 'xml_parsebuffer_fuzzer_UTF-16BE', 'xml_parse_fuzzer_UTF-16', 'xml_parsebuffer_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-16BE', 'xml_parse_fuzzer_US-ASCII', 'xml_parse_fuzzer_UTF-8', 'xml_parsebuffer_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-16', 'xml_parse_fuzzer_ISO-8859-1', 'xml_parsebuffer_fuzzer_UTF-8', 'xml_parse_fuzzer_UTF-16LE']

Directories in report

Directory
/src/expat/expat/fuzz/
/src/expat/expat/lib/

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
xml_parsebuffer_fuzzer_UTF-16LE fuzzerLogFile-0-O0aVROr53b.data fuzzerLogFile-0-O0aVROr53b.data.yaml xml_parsebuffer_fuzzer_UTF-16LE.covreport
xml_parsebuffer_fuzzer_UTF-16BE fuzzerLogFile-0-obNvEkv3Ij.data fuzzerLogFile-0-obNvEkv3Ij.data.yaml xml_parsebuffer_fuzzer_UTF-16BE.covreport
xml_parse_fuzzer_UTF-16 fuzzerLogFile-0-YjyVledzOW.data fuzzerLogFile-0-YjyVledzOW.data.yaml xml_parse_fuzzer_UTF-16.covreport
xml_parsebuffer_fuzzer_US-ASCII fuzzerLogFile-0-adldaLCCM7.data fuzzerLogFile-0-adldaLCCM7.data.yaml xml_parsebuffer_fuzzer_US-ASCII.covreport
xml_parse_fuzzer_UTF-16BE fuzzerLogFile-0-TcSk3DMVEw.data fuzzerLogFile-0-TcSk3DMVEw.data.yaml xml_parse_fuzzer_UTF-16BE.covreport
xml_parse_fuzzer_US-ASCII fuzzerLogFile-0-tqEIR9OwoW.data fuzzerLogFile-0-tqEIR9OwoW.data.yaml xml_parse_fuzzer_US-ASCII.covreport
xml_parse_fuzzer_UTF-8 fuzzerLogFile-0-J2cFRttJY5.data fuzzerLogFile-0-J2cFRttJY5.data.yaml xml_parse_fuzzer_UTF-8.covreport
xml_parsebuffer_fuzzer_ISO-8859-1 fuzzerLogFile-0-bAGVb1bDqx.data fuzzerLogFile-0-bAGVb1bDqx.data.yaml xml_parsebuffer_fuzzer_ISO-8859-1.covreport
xml_parsebuffer_fuzzer_UTF-16 fuzzerLogFile-0-9vwksIr4ET.data fuzzerLogFile-0-9vwksIr4ET.data.yaml xml_parsebuffer_fuzzer_UTF-16.covreport
xml_parse_fuzzer_ISO-8859-1 fuzzerLogFile-0-3ec7l4NWDp.data fuzzerLogFile-0-3ec7l4NWDp.data.yaml xml_parse_fuzzer_ISO-8859-1.covreport
xml_parsebuffer_fuzzer_UTF-8 fuzzerLogFile-0-KpGDFvQnKB.data fuzzerLogFile-0-KpGDFvQnKB.data.yaml xml_parsebuffer_fuzzer_UTF-8.covreport
xml_parse_fuzzer_UTF-16LE fuzzerLogFile-0-MBKLKr0Bnk.data fuzzerLogFile-0-MBKLKr0Bnk.data.yaml xml_parse_fuzzer_UTF-16LE.covreport