High level conclusions

Fuzzers reach 39.65% of cyclomatic complexity.

Fuzzers reach 40.63% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

102 / 251

Cyclomatic complexity statically reachable by fuzzers

652 / 1644

Runtime code coverage of functions

92 / 251

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: gd_target

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	7	53.8%
gold	[1:9]	5	38.4%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	1	7.69%
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
7	5	LLVMFuzzerTestOneInput	call site: 00005	gdFree

Runtime coverage analysis

Covered functions

6

Functions that are reachable but not covered

2

Reachable functions

7

Percentage of reachable functions covered

71.43%

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
/src/parser_target.cc	1
gd_gd.c	2
gd.c	3
gdhelpers.c	1

Fuzzer: tiff_target

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	7	53.8%
gold	[1:9]	5	38.4%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	1	7.69%
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
7	5	LLVMFuzzerTestOneInput	call site: 00005	gdFree

Runtime coverage analysis

Covered functions

6

Functions that are reachable but not covered

2

Reachable functions

7

Percentage of reachable functions covered

71.43%

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
/src/parser_target.cc	1
gd_tiff.c	2
gd.c	3
gdhelpers.c	1

Fuzzer: png_target

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	7	70.0%
gold	[1:9]	2	20.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	1	10.0%
All colors	10	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
7	2	LLVMFuzzerTestOneInput	call site: 00002	gdFree

Runtime coverage analysis

Covered functions

2

Functions that are reachable but not covered

2

Reachable functions

4

Percentage of reachable functions covered

50.0%

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
/src/parser_target.cc	1
gd_png.c	1
gd.c	1
gdhelpers.c	1

Fuzzer: webp_target

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	7	53.8%
gold	[1:9]	5	38.4%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	1	7.69%
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
7	5	LLVMFuzzerTestOneInput	call site: 00005	gdFree

Runtime coverage analysis

Covered functions

6

Functions that are reachable but not covered

2

Reachable functions

7

Percentage of reachable functions covered

71.43%

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
/src/parser_target.cc	1
gd_webp.c	2
gd.c	3
gdhelpers.c	1

Fuzzer: gd2_target

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	7	53.8%
gold	[1:9]	5	38.4%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	1	7.69%
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
7	5	LLVMFuzzerTestOneInput	call site: 00005	gdFree

Runtime coverage analysis

Covered functions

6

Functions that are reachable but not covered

2

Reachable functions

7

Percentage of reachable functions covered

71.43%

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
/src/parser_target.cc	1
gd_gd2.c	2
gd.c	3
gdhelpers.c	1

Fuzzer: jpeg_target

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	7	53.8%
gold	[1:9]	5	38.4%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	1	7.69%
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
7	5	LLVMFuzzerTestOneInput	call site: 00005	gdFree

Runtime coverage analysis

Covered functions

6

Functions that are reachable but not covered

2

Reachable functions

7

Percentage of reachable functions covered

71.43%

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
/src/parser_target.cc	1
gd_jpeg.c	2
gd.c	3
gdhelpers.c	1

Fuzzer: gd_image_string_fuzzer

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	32	53.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	2	3.33%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	26	43.3%
All colors	60	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
0	5	1 : View List ['gd_error_ex']	0	5	overflow2	call site: 00003	/src/libgd/src/gd_security.c:27
0	0	None	41	329	gdImageBrushApply	call site: 00027	/src/libgd/src/gd.c:1319
0	0	None	21	237	gdImageTileApply	call site: 00031	/src/libgd/src/gd.c:1400
0	0	None	0	72	gdImageSetPixel	call site: 00024	/src/libgd/src/gd.c:1251
0	0	None	0	72	gdImageSetPixel	call site: 00025	/src/libgd/src/gd.c:1263
0	0	None	0	14	gdImageCreateTrueColor	call site: 00008	/src/libgd/src/gd.c:305
0	0	None	0	14	gdImageDestroy	call site: 00052	/src/libgd/src/gd.c:390
0	0	None	0	10	gdImageCreateTrueColor	call site: 00009	/src/libgd/src/gd.c:311
0	0	None	0	10	gdImageCreateTrueColor	call site: 00011	/src/libgd/src/gd.c:322
0	0	None	0	6	gdImageDestroy	call site: 00056	/src/libgd/src/gd.c:402
0	0	None	0	0	gdImageCreateTrueColor	call site: 00006	/src/libgd/src/gd.c:297
0	0	None	0	0	gdImageCreateTrueColor	call site: 00007	/src/libgd/src/gd.c:300

Runtime coverage analysis

Covered functions

21

Functions that are reachable but not covered

8

Reachable functions

28

Percentage of reachable functions covered

71.43%

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
/src/gd_image_string_fuzzer.cc	1
gd.c	16
gd_security.c	1
gdhelpers.c	3
gdfontg.c	1
gdfontl.c	1
gdfontmb.c	1
gdfonts.c	1
gdfontt.c	1

Fuzzer: wbmp_target

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	49	46.2%
gold	[1:9]	2	1.88%
yellow	[10:29]	3	2.83%
greenyellow	[30:49]	1	0.94%
lawngreen	50+	51	48.1%
All colors	106	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
10	10	3 : View List ['gdLayerOverlay', 'gdAlphaBlend', 'gdLayerMultiply']	10	10	gdImageSetPixel	call site: 00070	/src/libgd/src/gd.c:1286
0	2	1 : View List ['gdMalloc']	0	2	allocDynamic	call site: 00006	/src/libgd/src/gd_io_dp.c:327
0	2	1 : View List ['gdFree']	0	2	readwbmp	call site: 00047	/src/libgd/src/wbmp.c:182
0	0	None	0	135	gdImageCreateFromWBMPPtr	call site: 00002	/src/libgd/src/gd_wbmp.c:259
0	0	None	0	14	gdImageCreate	call site: 00055	/src/libgd/src/gd.c:198
0	0	None	0	10	gdImageCreate	call site: 00057	/src/libgd/src/gd.c:204
0	0	None	0	10	gdImageCreate	call site: 00059	/src/libgd/src/gd.c:217
0	0	None	0	10	gdImageDestroy	call site: 00101	/src/libgd/src/gd.c:396
0	0	None	0	6	gdImageDestroy	call site: 00102	/src/libgd/src/gd.c:402
0	0	None	0	4	gdFreeDynamicCtx	call site: 00031	/src/libgd/src/gd_io_dp.c:158
0	0	None	0	0	gdImageCreate	call site: 00052	/src/libgd/src/gd.c:186
0	0	None	0	0	gdImageCreate	call site: 00054	/src/libgd/src/gd.c:193

Runtime coverage analysis

Covered functions

27

Functions that are reachable but not covered

18

Reachable functions

44

Percentage of reachable functions covered

59.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.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/parser_target.cc	1
gd_wbmp.c	3
gd_io_dp.c	12
gdhelpers.c	4
gd_security.c	1
gd.c	16
wbmp.c	4
gd_io.c	1

Fuzzer: tga_target

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	25	24.7%
gold	[1:9]	4	3.96%
yellow	[10:29]	8	7.92%
greenyellow	[30:49]	5	4.95%
lawngreen	50+	59	58.4%
All colors	101	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
0	5	1 : View List ['gd_error']	0	7	read_image_tga	call site: 00059	/src/libgd/src/gd_tga.c:280
0	2	1 : View List ['gdMalloc']	0	2	allocDynamic	call site: 00006	/src/libgd/src/gd_io_dp.c:327
0	0	None	0	147	gdImageCreateFromTgaCtx	call site: 00035	/src/libgd/src/gd_tga.c:73
0	0	None	0	14	gdImageCreateTrueColor	call site: 00078	/src/libgd/src/gd.c:305
0	0	None	0	14	gdImageDestroy	call site: 00094	/src/libgd/src/gd.c:390
0	0	None	0	10	gdImageCreateTrueColor	call site: 00079	/src/libgd/src/gd.c:311
0	0	None	0	10	gdImageCreateTrueColor	call site: 00081	/src/libgd/src/gd.c:322
0	0	None	0	7	gdImageCreateFromTgaCtx	call site: 00074	/src/libgd/src/gd_tga.c:97
0	0	None	0	6	gdImageDestroy	call site: 00097	/src/libgd/src/gd.c:402
0	0	None	0	4	gdFreeDynamicCtx	call site: 00031	/src/libgd/src/gd_io_dp.c:158
0	0	None	0	0	gdImageCreateTrueColor	call site: 00075	/src/libgd/src/gd.c:294
0	0	None	0	0	gdImageCreateTrueColor	call site: 00076	/src/libgd/src/gd.c:297

Runtime coverage analysis

Covered functions

27

Functions that are reachable but not covered

10

Reachable functions

36

Percentage of reachable functions covered

72.22%

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
/src/parser_target.cc	1
gd_tga.c	5
gd_io_dp.c	12
gdhelpers.c	4
gd_security.c	1
gd.c	7
gd_io.c	1
gd_transform.c	3

Fuzzer: gif_target

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	49	41.8%
gold	[1:9]	2	1.70%
yellow	[10:29]	6	5.12%
greenyellow	[30:49]	1	0.85%
lawngreen	50+	59	50.4%
All colors	117	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
10	10	3 : View List ['gdLayerOverlay', 'gdAlphaBlend', 'gdLayerMultiply']	10	10	gdImageSetPixel	call site: 00085	/src/libgd/src/gd.c:1286
0	2	1 : View List ['gdMalloc']	0	2	allocDynamic	call site: 00006	/src/libgd/src/gd_io_dp.c:327
0	0	None	0	204	gdImageCreateFromGifPtr	call site: 00002	/src/libgd/src/gd_gif_in.c:183
0	0	None	0	14	gdImageCreate	call site: 00056	/src/libgd/src/gd.c:198
0	0	None	0	10	gdImageCreate	call site: 00058	/src/libgd/src/gd.c:204
0	0	None	0	10	gdImageCreate	call site: 00060	/src/libgd/src/gd.c:217
0	0	None	0	10	gdImageDestroy	call site: 00067	/src/libgd/src/gd.c:396
0	0	None	0	6	gdImageDestroy	call site: 00068	/src/libgd/src/gd.c:402
0	0	None	0	4	gdFreeDynamicCtx	call site: 00031	/src/libgd/src/gd_io_dp.c:158
0	0	None	0	0	gdImageCreate	call site: 00055	/src/libgd/src/gd.c:193
0	0	None	0	0	gdImageColorTransparent	call site: 00114	/src/libgd/src/gd.c:904
0	0	None	0	0	gdImageColorTransparent	call site: 00114	/src/libgd/src/gd.c:909

Runtime coverage analysis

Covered functions

29

Functions that are reachable but not covered

21

Reachable functions

49

Percentage of reachable functions covered

57.14%

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
/src/parser_target.cc	1
gd_gif_in.c	11
gd_io_dp.c	12
gdhelpers.c	4
gd_security.c	1
gd.c	15
gd_io.c	1

Fuzzer: bmp_target

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	51	28.1%
gold	[1:9]	0	0.0%
yellow	[10:29]	2	1.10%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	128	70.7%
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
0	105	5 : View List ['gdImageSetPixel', 'gdGetWordLSB', 'gdTell', 'gdSeek', 'gdGetByte']	0	105	bmp_read_direct	call site: 00163	/src/libgd/src/gd_bmp.c:774
0	105	5 : View List ['gdImageSetPixel', 'gdGetWordLSB', 'gdTell', 'gdSeek', 'gdGetByte']	0	105	bmp_read_direct	call site: 00163	/src/libgd/src/gd_bmp.c:780
0	2	1 : View List ['gdMalloc']	0	2	allocDynamic	call site: 00006	/src/libgd/src/gd_io_dp.c:327
0	0	None	12	22	dynamicSeek	call site: 00026	/src/libgd/src/gd_io_dp.c:189
0	0	None	12	22	dynamicSeek	call site: 00026	/src/libgd/src/gd_io_dp.c:196
0	0	None	0	632	gdImageCreateFromBmpCtx	call site: 00035	/src/libgd/src/gd_bmp.c:514
0	0	None	0	603	gdImageCreateFromBmpCtx	call site: 00045	/src/libgd/src/gd_bmp.c:528
0	0	None	0	150	bmp_read_4bit	call site: 00145	/src/libgd/src/gd_bmp.c:994
0	0	None	0	14	gdImageCreate	call site: 00093	/src/libgd/src/gd.c:198
0	0	None	0	14	gdImageCreateTrueColor	call site: 00083	/src/libgd/src/gd.c:305
0	0	None	0	10	gdImageCreate	call site: 00094	/src/libgd/src/gd.c:204
0	0	None	0	10	gdImageCreate	call site: 00096	/src/libgd/src/gd.c:217

Runtime coverage analysis

Covered functions

40

Functions that are reachable but not covered

15

Reachable functions

54

Percentage of reachable functions covered

72.22%

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
/src/parser_target.cc	1
gd_bmp.c	13
gd_io_dp.c	12
gdhelpers.c	4
gd_security.c	1
gd.c	15
gd_io.c	6

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
gdImageArc	/src/libgd/src/gd.c	8	['struct.gdImageStruct *', 'int ', 'int ', 'int ', 'int ', 'int ', 'int ', 'int ']	5	0	44	3	2	35	0	274	194
gdImageBmpPtr	/src/libgd/src/gd_bmp.c	3	['struct.gdImageStruct *', 'int *', 'int ']	5	0	66	9	4	52	0	205	115
gdImageFill	/src/libgd/src/gd.c	4	['struct.gdImageStruct *', 'int ', 'int ', 'int ']	4	0	793	113	43	19	0	175	95
gdImageFillToBorder	/src/libgd/src/gd.c	5	['struct.gdImageStruct *', 'int ', 'int ', 'int ', 'int ']	4	0	457	87	30	11	1	122	60
gdImageCopyResampled	/src/libgd/src/gd.c	10	['struct.gdImageStruct *', 'struct.gdImageStruct *', 'int ', 'int ', 'int ', 'int ', 'int ', 'int ', 'int ', 'int ']	4	0	561	61	20	16	0	122	46
gdImageColorReplaceCallback	/src/libgd/src/gd.c	2	['struct.gdImageStruct *', 'func_type *']	4	0	258	35	12	22	0	123	43
gdImageClone	/src/libgd/src/gd.c	1	['struct.gdImageStruct *']	2	0	533	52	16	11	1	76	37

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

Functions statically reachable by fuzzers

148 / 251

Cyclomatic complexity statically reachable by fuzzers

1168 / 1644

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

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
gdImageBrushApply	73	9	12.32%	['gd_image_string_fuzzer', 'wbmp_target', 'gif_target', 'bmp_target']
gdImageTileApply	37	7	18.91%	['gd_image_string_fuzzer', 'wbmp_target', 'gif_target', 'bmp_target']

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/libgd/src/wbmp.c	['wbmp_target']	['wbmp_target']
/src/libgd/src/gd_gd.c	['gd_target']	['gd_target']
/src/libgd/src/gd_io_file.c	[]	[]
/src/libgd/src/gd_transform.c	['tga_target']	['tga_target']
/src/libgd/src/gd_gd2.c	['gd2_target']	['gd2_target']
/src/libgd/src/gd_security.c	['gd_image_string_fuzzer', 'wbmp_target', 'tga_target', 'gif_target', 'bmp_target']	['gd_image_string_fuzzer', 'wbmp_target', 'tga_target', 'gif_target', 'bmp_target']
/src/libgd/src/gdfonts.c	['gd_image_string_fuzzer']	['gd_image_string_fuzzer']
/src/libgd/src/gd_io_dp.c	['wbmp_target', 'tga_target', 'gif_target', 'bmp_target']	['wbmp_target', 'tga_target', 'gif_target', 'bmp_target']
/src/libgd/src/gd_jpeg.c	['jpeg_target']	['jpeg_target']
/src/libgd/src/gdhelpers.c	['gd_target', 'tiff_target', 'png_target', 'webp_target', 'gd2_target', 'jpeg_target', 'gd_image_string_fuzzer', 'wbmp_target', 'tga_target', 'gif_target', 'bmp_target']	['gd_image_string_fuzzer', 'wbmp_target', 'tga_target', 'gif_target', 'bmp_target']
/src/libgd/src/gd_tga.c	['tga_target']	['tga_target']
/src/libgd/src/gd_gif_in.c	['gif_target']	['gif_target']
/src/libgd/src/gd_io.c	['wbmp_target', 'tga_target', 'gif_target', 'bmp_target']	['wbmp_target', 'tga_target', 'gif_target', 'bmp_target']
/src/gd_image_string_fuzzer.cc	['gd_image_string_fuzzer']	['gd_image_string_fuzzer']
/src/libgd/src/gd.c	['gd_target', 'tiff_target', 'png_target', 'webp_target', 'gd2_target', 'jpeg_target', 'gd_image_string_fuzzer', 'wbmp_target', 'tga_target', 'gif_target', 'bmp_target']	['gd_target', 'tiff_target', 'webp_target', 'gd2_target', 'jpeg_target', 'gd_image_string_fuzzer', 'wbmp_target', 'tga_target', 'gif_target', 'bmp_target']
/src/libgd/src/gd_wbmp.c	['wbmp_target']	['wbmp_target']
/src/libgd/src/gd_tiff.c	['tiff_target']	['tiff_target']
/src/libgd/src/gd_png.c	['png_target']	['png_target']
/src/libgd/src/gd_bmp.c	['bmp_target']	['bmp_target']
/src/libgd/src/gdfontmb.c	['gd_image_string_fuzzer']	['gd_image_string_fuzzer']
/src/libgd/src/gdfontl.c	['gd_image_string_fuzzer']	['gd_image_string_fuzzer']
/src/libgd/src/gd_color.c	[]	[]
/src/libgd/src/gdfontt.c	['gd_image_string_fuzzer']	['gd_image_string_fuzzer']
/src/libgd/src/gd_webp.c	['webp_target']	['webp_target']
/src/parser_target.cc	['gd_target', 'tiff_target', 'png_target', 'webp_target', 'gd2_target', 'jpeg_target', 'wbmp_target', 'tga_target', 'gif_target', 'bmp_target']	['gd_target', 'tiff_target', 'png_target', 'webp_target', 'gd2_target', 'jpeg_target', 'wbmp_target', 'tga_target', 'gif_target', 'bmp_target']
/src/libgd/src/gdfontg.c	['gd_image_string_fuzzer']	['gd_image_string_fuzzer']

Directories in report

Directory
/src/libgd/src/
/src/