High level conclusions

Fuzzers reach 99.39% of cyclomatic complexity.

Fuzzers reach 99.37% of all functions.

Fuzzers reach 77.88% code coverage.

Fuzzer fuzz_ppd_gen_conflicts is blocked:

The runtime code coverage of fuzz_ppd_gen_conflicts covers 24.43% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_cups is blocked:

The runtime code coverage of fuzz_cups covers 26.50% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_raster is blocked:

The runtime code coverage of fuzz_raster covers 22.22% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Reachability and coverage overview

Functions statically reachable by fuzzers

319 / 321

Cyclomatic complexity statically reachable by fuzzers

4125 / 4150

Runtime code coverage of functions

250 / 321

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	Runtime reached by Fuzzers	Combined 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: fuzz_array

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	15	25.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	43	74.1%
All colors	58	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
4	19	cupsArrayAdd	call site: 00019	cups_array_find
3	14	LLVMFuzzerTestOneInput	call site: 00014	cupsArrayGetUserData
2	11	LLVMFuzzerTestOneInput	call site: 00011	printf
1	27	cupsArrayCurrent	call site: 00027	printf
1	33	cupsArrayGetLast	call site: 00033	printf
1	39	cupsArrayFind	call site: 00039	printf
1	41	LLVMFuzzerTestOneInput	call site: 00041	printf
1	49	LLVMFuzzerTestOneInput	call site: 00049	printf
1	56	LLVMFuzzerTestOneInput	call site: 00056	abort

Runtime coverage analysis

Covered functions

24

Functions that are reachable but not covered

9

Reachable functions

33

Percentage of reachable functions covered

72.73%

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/cups/ossfuzz/fuzz_array.c	1
/src/cups/ossfuzz/fuzz_helpers.cpp	1
/src/cups/cups/array.c	22

Fuzzer: fuzz_raster

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	85	54.4%
gold	[1:9]	24	15.3%
yellow	[10:29]	1	0.64%
greenyellow	[30:49]	5	3.20%
lawngreen	50+	41	26.2%
All colors	156	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
52	15	cups_globals_init	call site: 00015	cupsFreeOptions
9	88	cupsCopyString	call site: 00088	validate_end
6	115	_cupsRasterNew	call site: 00115	cups_raster_io
5	123	cups_read_fd	call site: 00123	_cupsRasterNew
4	83	cups_globals_alloc	call site: 00083	cupsCopyString
3	99	_cupsRasterNew	call site: 00099	_cupsRasterAddError
3	148	cups_raster_update	call site: 00148	_cupsRasterAddError
1	104	_cupsRasterAddError	call site: 00104	realloc
1	106	_cupsRasterNew	call site: 00106	_cupsRasterAddError
1	133	cups_raster_read	call site: 00133	realloc

Runtime coverage analysis

Covered functions

18

Functions that are reachable but not covered

63

Reachable functions

81

Percentage of reachable functions covered

22.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/cups/ossfuzz/fuzz_raster.c	2
/src/cups/cups/raster-stubs.c	5
/src/cups/cups/raster-stream.c	6
/src/cups/cups/raster-error.c	2
/src/cups/cups/globals.c	4
/src/cups/cups/string.c	3
/src/cups/cups/thread.c	2
/src/cups/cups/array.c	4
/src/cups/cups/http.c	2
/src/cups/cups/./tls-openssl.c	2
/src/cups/cups/http-addr.c	1
/src/cups/cups/http-addrlist.c	1
/usr/include/openssl/x509.h	1
/src/cups/cups/file.c	4
/src/cups/cups/options.c	1

Fuzzer: fuzz_cups

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	76	31.5%
gold	[1:9]	19	7.88%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	146	60.5%
All colors	241	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
52	9	cups_globals_init	call site: 00009	cupsFreeOptions
10	226	error_object	call site: 00226	_cupsRasterAddError
8	83	cupsCopyString	call site: 00083	snprintf
4	77	cups_globals_alloc	call site: 00077	cupsCopyString
1	3	_cupsRasterExecPS	call site: 00003	_cupsRasterAddError
1	97	new_stack	call site: 00097	_cupsRasterAddError

Runtime coverage analysis

Covered functions

22

Functions that are reachable but not covered

61

Reachable functions

83

Percentage of reachable functions covered

26.51%

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/cups/ossfuzz/fuzz_cups.c	1
/src/cups/cups/raster-interpret.c	13
/src/cups/cups/raster-error.c	1
/src/cups/cups/globals.c	4
/src/cups/cups/string.c	4
/src/cups/cups/thread.c	2
/src/cups/cups/array.c	4
/src/cups/cups/http.c	2
/src/cups/cups/./tls-openssl.c	2
/src/cups/cups/http-addr.c	1
/src/cups/cups/http-addrlist.c	1
/usr/include/openssl/x509.h	1
/src/cups/cups/file.c	4
/src/cups/cups/options.c	1
/src/cups/cups/./string-private.h	1

Fuzzer: fuzz_http_core

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	310	63.7%
gold	[1:9]	41	8.43%
yellow	[10:29]	6	1.23%
greenyellow	[30:49]	11	2.26%
lawngreen	50+	118	24.2%
All colors	486	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
87	372	httpAddrLength	call site: 00372	_cupsSetError
59	197	_cupsSetError	call site: 00197	_cupsLangString
43	87	_cupsStrFree	call site: 00087	cupsFreeOptions
36	257	cupsArrayNew3	call site: 00257	cupsFileOpen
30	341	httpAddrGetList	call site: 00341	_cupsSetError
12	146	cups_globals_alloc	call site: 00146	cupsCopyString
9	317	httpAddrGetList	call site: 00317	_cupsSetError
5	187	httpAddrGetList	call site: 00187	_cupsSetError
4	26	httpAssembleURI	call site: 00026	strcmp
4	328	httpAddrGetList	call site: 00328	_cupsSetError
4	335	httpAddrGetList	call site: 00335	_cupsSetError
2	169	test_http_encoding_functions	call site: 00169	httpEncode64_3

Runtime coverage analysis

Covered functions

53

Functions that are reachable but not covered

118

Reachable functions

171

Percentage of reachable functions covered

30.99%

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/cups/ossfuzz/fuzz_http_core.c	8
/src/cups/cups/http.c	4
/src/cups/cups/globals.c	6
/src/cups/cups/thread.c	2
/src/cups/cups/./tls-openssl.c	3
/src/cups/cups/http-support.c	10
/src/cups/cups/string.c	7
/src/cups/cups/./string-private.h	3
/src/cups/cups/array.c	8
/src/cups/cups/http-addr.c	9
/src/cups/cups/http-addrlist.c	4
/usr/include/openssl/x509.h	1
/src/cups/cups/file.c	10
/src/cups/cups/options.c	1
/src/cups/cups/request.c	1
/src/cups/cups/language.c	14

Fuzzer: fuzz_ipp

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	395	60.6%
gold	[1:9]	96	14.7%
yellow	[10:29]	19	2.91%
greenyellow	[30:49]	3	0.46%
lawngreen	50+	138	21.1%
All colors	651	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
42	347	_cupsLangString	call site: 00347	_cupsSetError
37	246	_cupsStrAlloc	call site: 00246	_cupsSetError
35	430	cups_set_server_name	call site: 00430	cups_set_ssl_options
32	397	_cupsSetDefaults	call site: 00397	cups_read_client_conf
28	52	cupsMutexUnlock	call site: 00052	cupsFileClose
26	318	cups_fill	call site: 00318	cupsFileGets
19	522	_cupsSetDefaults	call site: 00522	cupsArrayNewStrings
17	9	cupsFileOpen	call site: 00009	cups_open
14	549	_cupsSetDefaults	call site: 00549	_cups_strcasecmp
13	138	_cups_tolower	call site: 00138	_cupsSetError
12	111	cups_globals_alloc	call site: 00111	cupsCopyString
12	124	_cupsGlobals	call site: 00124	cupsCopyString

Runtime coverage analysis

Covered functions

58

Functions that are reachable but not covered

128

Reachable functions

186

Percentage of reachable functions covered

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/cups/ossfuzz/fuzz_ipp.c	2
/src/cups/cups/file.c	12
/src/cups/cups/string.c	8
/src/cups/cups/http-addrlist.c	4
/src/cups/cups/globals.c	6
/src/cups/cups/thread.c	2
/src/cups/cups/array.c	13
/src/cups/cups/http.c	3
/src/cups/cups/./tls-openssl.c	3
/src/cups/cups/http-addr.c	5
/usr/include/openssl/x509.h	1
/src/cups/cups/options.c	1
/src/cups/cups/./string-private.h	4
/src/cups/cups/request.c	1
/src/cups/cups/language.c	14
/src/cups/cups/ipp.c	14
/src/cups/cups/usersys.c	16
/src/cups/cups/tls.c	1

Fuzzer: fuzz_ipp_gen

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	396	60.0%
gold	[1:9]	93	14.1%
yellow	[10:29]	18	2.73%
greenyellow	[30:49]	1	0.15%
lawngreen	50+	151	22.9%
All colors	659	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
42	343	_cupsLangString	call site: 00343	_cupsSetError
37	242	_cupsStrAlloc	call site: 00242	_cupsSetError
35	436	cups_set_server_name	call site: 00436	cups_set_ssl_options
32	403	_cupsSetDefaults	call site: 00403	cups_read_client_conf
26	314	cups_fill	call site: 00314	cupsFileGets
19	48	cupsMutexUnlock	call site: 00048	cupsFileClose
19	528	_cupsSetDefaults	call site: 00528	cupsArrayNewStrings
14	555	_cupsSetDefaults	call site: 00555	_cups_strcasecmp
13	134	_cups_tolower	call site: 00134	_cupsSetError
12	107	cups_globals_alloc	call site: 00107	cupsCopyString
12	120	_cupsGlobals	call site: 00120	cupsCopyString
8	83	cupsFileClose	call site: 00083	cupsFreeOptions

Runtime coverage analysis

Covered functions

60

Functions that are reachable but not covered

122

Reachable functions

182

Percentage of reachable functions covered

32.97%

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/cups/ossfuzz/fuzz_ipp_gen.c	1
/src/cups/cups/file.c	13
/src/cups/cups/string.c	8
/src/cups/cups/http-addrlist.c	4
/src/cups/cups/globals.c	6
/src/cups/cups/thread.c	2
/src/cups/cups/array.c	13
/src/cups/cups/http.c	3
/src/cups/cups/./tls-openssl.c	3
/src/cups/cups/http-addr.c	5
/usr/include/openssl/x509.h	1
/src/cups/cups/options.c	1
/src/cups/cups/./string-private.h	4
/src/cups/cups/request.c	1
/src/cups/cups/language.c	14
/src/cups/cups/ipp.c	14
/src/cups/cups/usersys.c	16
/src/cups/cups/tls.c	1

Fuzzer: fuzz_ppd_gen_conflicts

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	1283	74.8%
gold	[1:9]	32	1.86%
yellow	[10:29]	9	0.52%
greenyellow	[30:49]	6	0.35%
lawngreen	50+	383	22.3%
All colors	1713	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
786	926	LLVMFuzzerTestOneInput	call site: 00926	cupsMarkOptions
71	328	cups_fill	call site: 00328	_cupsSetError
49	97	cupsFileClose	call site: 00097	cupsFreeOptions
40	883	ppdClose	call site: 00883	ppd_update_filters
38	255	cups_array_add	call site: 00255	_cupsSetError
28	62	cupsMutexUnlock	call site: 00062	cupsFileClose
20	148	_cups_tolower	call site: 00148	_cupsSetError
17	19	cupsFileOpen	call site: 00019	cups_open
16	226	cupsArrayNew3	call site: 00226	cupsFileOpen
16	723	_ppdOpen	call site: 00723	ppdFindAttr
15	480	ppd_get_group	call site: 00480	cupsCopyString
13	212	cupsLangGet	call site: 00212	_cupsLangString

Runtime coverage analysis

Covered functions

65

Functions that are reachable but not covered

201

Reachable functions

266

Percentage of reachable functions covered

24.44%

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/cups/ossfuzz/fuzz_ppd_gen_conflicts.c	1
/src/cups/cups/ppd.c	27
/src/cups/cups/file.c	12
/src/cups/cups/string.c	11
/src/cups/cups/http-addrlist.c	4
/src/cups/cups/globals.c	6
/src/cups/cups/thread.c	2
/src/cups/cups/array.c	28
/src/cups/cups/http.c	3
/src/cups/cups/./tls-openssl.c	3
/src/cups/cups/http-addr.c	5
/usr/include/openssl/x509.h	1
/src/cups/cups/options.c	8
/src/cups/cups/./string-private.h	6
/src/cups/cups/request.c	1
/src/cups/cups/language.c	15
/src/cups/cups/transcode.c	2
/src/cups/cups/ppd-custom.c	2
/src/cups/cups/ppd-mark.c	9
/src/cups/cups/ppd-attr.c	2
/src/cups/cups/ppd-page.c	1
/src/cups/cups/ppd-cache.c	12
/src/cups/cups/ppd-conflicts.c	6
/src/cups/cups/pwg-media.c	13
/src/cups/cups/ipp.c	5

Fuzzer: fuzz_ppd_gen_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	853	52.1%
gold	[1:9]	14	0.85%
yellow	[10:29]	6	0.36%
greenyellow	[30:49]	6	0.36%
lawngreen	50+	757	46.2%
All colors	1636	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
449	1146	cupsMarkOptions	call site: 01146	_ppdCacheCreateWithPPD
71	328	cups_fill	call site: 00328	_cupsSetError
41	105	cupsFreeOptions	call site: 00105	cups_globals_alloc
37	256	_cupsStrAlloc	call site: 00256	_cupsSetError
28	62	cupsMutexUnlock	call site: 00062	cupsFileClose
20	148	_cups_tolower	call site: 00148	_cupsSetError
17	19	cupsFileOpen	call site: 00019	cups_open
14	226	cupsArrayNew3	call site: 00226	cupsFileOpen
13	212	cupsLangGet	call site: 00212	_cupsLangString
13	482	cupsCharsetToUTF8	call site: 00482	_cupsCharmapFlush
8	46	cupsCopyString	call site: 00046	httpAddrGetList
8	1613	cupsMarkOptions	call site: 01613	ppd_mark_choices

Runtime coverage analysis

Covered functions

100

Functions that are reachable but not covered

162

Reachable functions

262

Percentage of reachable functions covered

38.17%

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/cups/ossfuzz/fuzz_ppd_gen_1.c	1
/src/cups/cups/ppd.c	27
/src/cups/cups/file.c	12
/src/cups/cups/string.c	11
/src/cups/cups/http-addrlist.c	4
/src/cups/cups/globals.c	6
/src/cups/cups/thread.c	2
/src/cups/cups/array.c	26
/src/cups/cups/http.c	3
/src/cups/cups/./tls-openssl.c	3
/src/cups/cups/http-addr.c	5
/usr/include/openssl/x509.h	1
/src/cups/cups/options.c	8
/src/cups/cups/./string-private.h	6
/src/cups/cups/request.c	1
/src/cups/cups/language.c	15
/src/cups/cups/transcode.c	2
/src/cups/cups/ppd-custom.c	2
/src/cups/cups/ppd-mark.c	10
/src/cups/cups/ppd-attr.c	2
/src/cups/cups/ppd-page.c	1
/src/cups/cups/ppd-cache.c	12
/src/cups/cups/ppd-conflicts.c	4
/src/cups/cups/pwg-media.c	13
/src/cups/cups/ipp.c	5

Fuzzer: fuzz_ppd_gen_cache

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	930	42.0%
gold	[1:9]	122	5.51%
yellow	[10:29]	40	1.80%
greenyellow	[30:49]	12	0.54%
lawngreen	50+	1108	50.0%
All colors	2212	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
44	2027	_cupsConvertOptions	call site: 02027	cupsHashData
42	367	_cupsLangString	call site: 00367	_cupsSetError
37	266	_cupsStrAlloc	call site: 00266	_cupsSetError
35	1419	cups_set_server_name	call site: 01419	cups_set_ssl_options
32	1715	_cupsBufferGet	call site: 01715	ippWriteIO
26	338	cups_fill	call site: 00338	cupsFileGets
25	2072	_cupsConvertOptions	call site: 02072	ippAddInteger
21	2120	_cupsConvertOptions	call site: 02120	ippNew
20	1398	cupsFileGetConf	call site: 01398	cups_set_browse_domains
19	72	cupsMutexUnlock	call site: 00072	cupsFileClose
18	1177	_ppdCacheCreateWithPPD	call site: 01177	pwg_add_finishing
18	1804	ipp_read_io	call site: 01804	ipp_set_value

Runtime coverage analysis

Covered functions

173

Functions that are reachable but not covered

173

Reachable functions

346

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/cups/ossfuzz/fuzz_ppd_gen_cache.c	5
/src/cups/cups/ppd.c	27
/src/cups/cups/file.c	22
/src/cups/cups/string.c	11
/src/cups/cups/http-addrlist.c	4
/src/cups/cups/globals.c	6
/src/cups/cups/thread.c	2
/src/cups/cups/array.c	24
/src/cups/cups/http.c	3
/src/cups/cups/./tls-openssl.c	3
/src/cups/cups/http-addr.c	5
/usr/include/openssl/x509.h	1
/src/cups/cups/options.c	8
/src/cups/cups/./string-private.h	6
/src/cups/cups/request.c	1
/src/cups/cups/language.c	15
/src/cups/cups/transcode.c	2
/src/cups/cups/ppd-custom.c	2
/src/cups/cups/ppd-mark.c	4
/src/cups/cups/ppd-attr.c	2
/src/cups/cups/ppd-page.c	1
/src/cups/cups/ppd-cache.c	21
/src/cups/cups/pwg-media.c	13
/src/cups/cups/ipp.c	36
/src/cups/cups/usersys.c	16
/src/cups/cups/tls.c	1
/src/cups/cups/hash.c	2
/src/cups/cups/md5.c	4
/src/cups/cups/encode.c	2

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

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

Functions statically reachable by fuzzers

319 / 321

Cyclomatic complexity statically reachable by fuzzers

4125 / 4150

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	Runtime reached by Fuzzers	Combined 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 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.

/src/cups/ossfuzz/fuzz_array.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=['cupsArrayAdd', 'LLVMFuzzerTestOneInput', 'cupsArrayCurrent', 'cupsArrayGetLast', 'cupsArrayFind']

/src/cups/ossfuzz/fuzz_raster.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=['cups_globals_init', 'cupsCopyString', '_cupsRasterNew', 'cups_read_fd', 'cups_globals_alloc', 'cups_raster_update', '_cupsRasterAddError', 'cups_raster_read']

/src/cups/ossfuzz/fuzz_cups.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=['cups_globals_init', 'error_object', 'cupsCopyString', 'cups_globals_alloc', '_cupsRasterExecPS', 'new_stack']

/src/cups/ossfuzz/fuzz_http_core.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=['httpAddrLength', '_cupsSetError', '_cupsStrFree', 'cupsArrayNew3', 'httpAddrGetList', 'cups_globals_alloc', 'httpAssembleURI']

/src/cups/ossfuzz/fuzz_ipp.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=['_cupsLangString', '_cupsStrAlloc', 'cups_set_server_name', '_cupsSetDefaults', 'cupsMutexUnlock', 'cups_fill', 'cupsFileOpen', '_cups_tolower']

/src/cups/ossfuzz/fuzz_ipp_gen.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=['_cupsLangString', '_cupsStrAlloc', 'cups_set_server_name', '_cupsSetDefaults', 'cups_fill', 'cupsMutexUnlock', '_cups_tolower', 'cups_globals_alloc']

/src/cups/ossfuzz/fuzz_ppd_gen_conflicts.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=['LLVMFuzzerTestOneInput', 'cups_fill', 'cupsFileClose', 'ppdClose', 'cups_array_add', 'cupsMutexUnlock', '_cups_tolower', 'cupsFileOpen', 'cupsArrayNew3', '_ppdOpen']

/src/cups/ossfuzz/fuzz_ppd_gen_1.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=['cupsMarkOptions', 'cups_fill', 'cupsFreeOptions', '_cupsStrAlloc', 'cupsMutexUnlock', '_cups_tolower', 'cupsFileOpen', 'cupsArrayNew3', 'cupsLangGet', 'cupsCharsetToUTF8']

/src/cups/ossfuzz/fuzz_ppd_gen_cache.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=['_cupsConvertOptions', '_cupsLangString', '_cupsStrAlloc', 'cups_set_server_name', '_cupsBufferGet', 'cups_fill', 'cupsFileGetConf', 'cupsMutexUnlock']

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
cups_globals_alloc	89	41	46.06%	['fuzz_ppd_gen_1', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_cache', 'fuzz_http_core', 'fuzz_cups', 'fuzz_raster']
_cupsRasterNew	81	44	54.32%	['fuzz_raster']
cupsFileOpen	66	35	53.03%	['fuzz_ppd_gen_1', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_cache', 'fuzz_http_core']
_cupsMessageLoad	75	18	24.0%	['fuzz_ppd_gen_1', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_cache', 'fuzz_http_core']
cupsSetServer	48	20	41.66%	['fuzz_ipp_gen', 'fuzz_ipp', 'fuzz_ppd_gen_cache']
_cupsSetDefaults	198	52	26.26%	['fuzz_ipp_gen', 'fuzz_ipp', 'fuzz_ppd_gen_cache']
cups_open	49	21	42.85%	['fuzz_ppd_gen_1', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_cache', 'fuzz_http_core']
cupsCharsetToUTF8	66	34	51.51%	['fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']
cupsMarkOptions	183	47	25.68%	['fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1']
cupsFilePrintf	58	29	50.0%	['fuzz_ppd_gen_cache']
ippContainsString	46	9	19.56%	['fuzz_ppd_gen_cache']
ippFindNextAttribute	83	33	39.75%	['fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']
_cupsConvertOptions	290	88	30.34%	['fuzz_ppd_gen_cache']
_ppdCacheGetFinishingOptions	37	9	24.32%	['fuzz_ppd_gen_cache']
_ppdCacheGetFinishingValues	48	14	29.16%	['fuzz_ppd_gen_cache']
pwgInitSize	114	48	42.10%	['fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']

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/cups/cups/raster-stubs.c	['fuzz_raster']	['fuzz_raster']
/src/cups/cups/encode.c	['fuzz_ppd_gen_cache']	[]
/src/cups/cups/ipp.c	['fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	['fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_cache']
/src/cups/cups/tls.c	['fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_cache']	['fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_cache']
/usr/lib/gcc/x86_64-linux-gnu/9/../../../../include/c++/9/limits	[]	[]
/src/cups/cups/ppd-custom.c	['fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	['fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']
/src/cups/cups/usersys.c	['fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_cache']	['fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_cache']
/src/cups/cups/thread.c	['fuzz_raster', 'fuzz_cups', 'fuzz_http_core', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	['fuzz_http_core', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']
/src/cups/ossfuzz/fuzz_ppd_gen_conflicts.c	['fuzz_ppd_gen_conflicts']	['fuzz_ppd_gen_conflicts']
/src/cups/cups/http-support.c	['fuzz_http_core']	['fuzz_http_core']
/src/cups/cups/transcode.c	['fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	['fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']
/src/cups/cups/globals.c	['fuzz_raster', 'fuzz_cups', 'fuzz_http_core', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	['fuzz_raster', 'fuzz_cups', 'fuzz_http_core', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_cache']
/src/cups/cups/array.c	['fuzz_array', 'fuzz_raster', 'fuzz_cups', 'fuzz_http_core', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	['fuzz_array', 'fuzz_http_core', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']
/src/cups/cups/./tls-openssl.c	['fuzz_raster', 'fuzz_cups', 'fuzz_http_core', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	[]
/src/cups/ossfuzz/fuzz_ppd_gen_cache.c	['fuzz_ppd_gen_cache']	['fuzz_ppd_gen_cache']
/src/cups/cups/md5.c	['fuzz_ppd_gen_cache']	[]
/src/cups/cups/./string-private.h	['fuzz_cups', 'fuzz_http_core', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	[]
/src/cups/cups/options.c	['fuzz_raster', 'fuzz_cups', 'fuzz_http_core', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	['fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']
/src/cups/ossfuzz/fuzz_ppd_gen_1.c	['fuzz_ppd_gen_1']	['fuzz_ppd_gen_1']
/src/cups/cups/ppd-page.c	['fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	['fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']
/src/cups/cups/string.c	['fuzz_raster', 'fuzz_cups', 'fuzz_http_core', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	['fuzz_raster', 'fuzz_cups', 'fuzz_http_core', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']
/src/cups/cups/language.c	['fuzz_http_core', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	['fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']
/src/cups/ossfuzz/fuzz_cups.c	['fuzz_cups']	['fuzz_cups']
/src/cups/cups/ppd-conflicts.c	['fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1']	['fuzz_ppd_gen_1']
/src/cups/cups/ppd-mark.c	['fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	['fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']
/src/cups/cups/http-addr.c	['fuzz_raster', 'fuzz_cups', 'fuzz_http_core', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	['fuzz_http_core']
/src/cups/ossfuzz/fuzz_ipp.c	['fuzz_ipp']	['fuzz_ipp']
/src/cups/ossfuzz/fuzz_array.c	['fuzz_array']	['fuzz_array']
/src/cups/cups/raster-stream.c	['fuzz_raster']	['fuzz_raster']
/src/cups/cups/request.c	['fuzz_http_core', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	['fuzz_http_core', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_cache']
/src/cups/cups/ppd-cache.c	['fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	['fuzz_ppd_gen_cache']
/src/cups/cups/raster-error.c	['fuzz_raster', 'fuzz_cups']	['fuzz_raster', 'fuzz_cups']
/src/cups/cups/raster-interpret.c	['fuzz_cups']	['fuzz_cups']
/usr/include/openssl/x509.h	['fuzz_raster', 'fuzz_cups', 'fuzz_http_core', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	[]
/src/cups/ossfuzz/fuzz_helpers.cpp	['fuzz_array']	['fuzz_array']
/src/cups/ossfuzz/fuzz_raster.c	['fuzz_raster']	['fuzz_raster']
/src/cups/cups/file.c	['fuzz_raster', 'fuzz_cups', 'fuzz_http_core', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	['fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']
/src/cups/cups/ppd-attr.c	['fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	['fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']
/src/cups/cups/hash.c	['fuzz_ppd_gen_cache']	[]
/src/cups/cups/http.c	['fuzz_raster', 'fuzz_cups', 'fuzz_http_core', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	['fuzz_http_core']
/src/cups/cups/pwg-media.c	['fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	['fuzz_ppd_gen_cache']
/src/cups/cups/ppd.c	['fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	['fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']
/src/cups/ossfuzz/fuzz_http_core.c	['fuzz_http_core']	['fuzz_http_core']
/src/cups/cups/http-addrlist.c	['fuzz_raster', 'fuzz_cups', 'fuzz_http_core', 'fuzz_ipp', 'fuzz_ipp_gen', 'fuzz_ppd_gen_conflicts', 'fuzz_ppd_gen_1', 'fuzz_ppd_gen_cache']	['fuzz_http_core']
/src/cups/ossfuzz/fuzz_ipp_gen.c	['fuzz_ipp_gen']	['fuzz_ipp_gen']

Directories in report

Directory
/usr/include/openssl/
/src/cups/ossfuzz/
/usr/lib/gcc/x86_64-linux-gnu/9/../../../../include/c++/9/
/src/cups/cups/
/src/cups/cups/./