High level conclusions

Fuzzers reach 49.37% of cyclomatic complexity.

Fuzzers reach 54.20% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

1024 / 1889

Cyclomatic complexity statically reachable by fuzzers

7885 / 15969

Runtime code coverage of functions

765 / 1889

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_regexp

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	444	73.1%
gold	[1:9]	90	14.8%
yellow	[10:29]	7	1.15%
greenyellow	[30:49]	7	1.15%
lawngreen	50+	59	9.71%
All colors	607	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
169	150	re_parse_term	call site: 00150	re_parse_char_class
50	356	get_class_atom	call site: 00356	re_parse_class_set_operand
41	75	re_parse_term	call site: 00075	re_parse_group_name
29	575	lre_exec_backtrack	call site: 00575	lre_canonicalize
22	123	re_parse_term	call site: 00123	re_has_named_captures
19	335	lre_canonicalize	call site: 00335	parse_class_string_disjunction
14	320	lre_case_folding_entry	call site: 00320	cr_sort_and_remove_overlap
13	421	re_emit_char	call site: 00421	re_emit_range
12	408	re_emit_op_u16	call site: 00408	rqsort
10	532	lre_exec_backtrack	call site: 00532	lre_is_space
8	40	re_parse_term	call site: 00040	re_parse_disjunction
8	518	lre_exec_backtrack	call site: 00518	is_line_terminator

Runtime coverage analysis

Covered functions

55

Functions that are reachable but not covered

84

Reachable functions

139

Percentage of reachable functions covered

39.57%

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
fuzz/fuzz_regexp.c	4
libregexp.c	57
cutils.c	14
./cutils.h	14
./libunicode.h	10
libunicode.c	32

Fuzzer: fuzz_compile

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	4232	72.1%
gold	[1:9]	897	15.2%
yellow	[10:29]	288	4.91%
greenyellow	[30:49]	52	0.88%
lawngreen	50+	394	6.72%
All colors	5863	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
541	2591	JS_DefinePropertyValueUint32	call site: 02591	JS_IteratorNext
405	4072	lre_js_is_ident_next	call site: 04072	js_regexp_set_internal
194	2338	JS_CallInternal	call site: 02338	JS_NewSymbolFromAtom
183	5038	js_std_add_helpers	call site: 05038	js_print
158	2164	JS_CallInternal	call site: 02164	JS_ThrowInternalError
135	3197	js_async_function_resume	call site: 03197	js_promise_resolve
104	4868	string_buffer_putc_slow	call site: 04868	json_parse_value
99	5709	JS_ReadModule	call site: 05709	JS_ReadObjectRec
75	2088	JS_CallInternal	call site: 02088	JS_ThrowReferenceErrorUninitialized2
75	4621	JS_AddIntrinsicTypedArrays	call site: 04621	js_typed_array_constructor_obj
74	1711	JS_ToInt32	call site: 01711	JS_ToNumberFree
72	3990	dbuf_put_u32	call site: 03990	re_parse_disjunction

Runtime coverage analysis

Covered functions

595

Functions that are reachable but not covered

592

Reachable functions

1053

Percentage of reachable functions covered

43.78%

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
fuzz/fuzz_compile.c	1
quickjs.c	785
./list.h	6
./cutils.h	29
./quickjs.h	23
dtoa.c	37
cutils.c	18
./libunicode.h	9
libunicode.c	32
libregexp.c	51
fuzz/fuzz_common.c	3
quickjs-libc.c	34

Fuzzer: fuzz_eval

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	3649	67.4%
gold	[1:9]	423	7.82%
yellow	[10:29]	586	10.8%
greenyellow	[30:49]	176	3.25%
lawngreen	50+	572	10.5%
All colors	5406	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
297	4074	lre_is_id_continue	call site: 04074	re_parse_disjunction
186	2944	JS_CallInternal	call site: 02944	js_binary_logic_slow
183	5038	js_std_add_helpers	call site: 05038	js_print
130	2402	JS_ConcatString3	call site: 02402	JS_DefinePropertyValue
104	3197	js_async_function_resume	call site: 03197	js_promise_resolve
104	3817	JS_AddIntrinsicDate	call site: 03817	js_Date_parse
94	4878	ident_realloc	call site: 04878	json_parse_value
81	2753	js_binary_arith_slow	call site: 02753	js_bigint_add
52	4621	JS_AddIntrinsicTypedArrays	call site: 04621	js_typed_array_constructor_obj
50	1044	JS_NewObject	call site: 01044	js_build_arguments
49	1840	js_atof	call site: 01840	JS_ThrowOutOfMemory
49	3367	JS_EvalFunctionInternal	call site: 03367	JS_ThrowTypeError

Runtime coverage analysis

Covered functions

707

Functions that are reachable but not covered

478

Reachable functions

990

Percentage of reachable functions covered

51.72%

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
fuzz/fuzz_eval.c	1
quickjs.c	723
./list.h	6
./cutils.h	28
./quickjs.h	23
dtoa.c	37
cutils.c	18
./libunicode.h	9
libunicode.c	32
libregexp.c	51
fuzz/fuzz_common.c	3
quickjs-libc.c	34

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
__JS_EvalInternal	/src/quickjs/quickjs.c	8	['N/A', 'size_t', 'size_t', 'N/A', 'size_t', 'N/A', 'int', 'int']	96	0	334	57	20	830	0	7589	2755
js_regexp_Symbol_replace	/src/quickjs/quickjs.c	5	['N/A', 'size_t', 'size_t', 'int', 'N/A']	70	0	712	120	49	664	0	5303	309
js_json_to_str	/src/quickjs/quickjs.c	5	['N/A', 'N/A', 'size_t', 'size_t', 'N/A']	75	0	775	140	54	653	3	5001	252
js_string_normalize	/src/quickjs/quickjs.c	5	['N/A', 'size_t', 'size_t', 'int', 'N/A']	69	0	150	31	13	646	0	4856	127
js_typed_array_indexOf	/src/quickjs/quickjs.c	6	['N/A', 'size_t', 'size_t', 'int', 'N/A', 'int']	71	0	930	227	93	631	0	4814	115
js_os_exec	/src/quickjs/quickjs-libc.c	5	['N/A', 'size_t', 'size_t', 'int', 'N/A']	71	0	745	163	61	642	0	4815	111
js_set_difference	/src/quickjs/quickjs.c	5	['N/A', 'size_t', 'size_t', 'int', 'N/A']	72	0	248	39	17	638	0	4813	90

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

Functions statically reachable by fuzzers

1280 / 1889

Cyclomatic complexity statically reachable by fuzzers

11566 / 15969

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.

fuzz/fuzz_regexp.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=['re_parse_term', 'get_class_atom', 'lre_exec_backtrack', 'lre_canonicalize', 'lre_case_folding_entry', 're_emit_char', 're_emit_op_u16']

fuzz/fuzz_compile.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=['JS_DefinePropertyValueUint32', 'lre_js_is_ident_next', 'JS_CallInternal', 'js_std_add_helpers', 'js_async_function_resume', 'string_buffer_putc_slow', 'JS_ReadModule', 'JS_AddIntrinsicTypedArrays']

fuzz/fuzz_eval.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=['lre_is_id_continue', 'JS_CallInternal', 'js_std_add_helpers', 'JS_ConcatString3', 'js_async_function_resume', 'JS_AddIntrinsicDate', 'ident_realloc', 'js_binary_arith_slow', 'JS_AddIntrinsicTypedArrays', 'JS_NewObject']

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
re_parse_term	471	222	47.13%	['fuzz_eval', 'fuzz_regexp', 'fuzz_compile']
get_class_atom	165	48	29.09%	['fuzz_eval', 'fuzz_regexp', 'fuzz_compile']
lre_case_conv_entry	88	24	27.27%	['fuzz_eval', 'fuzz_regexp', 'fuzz_compile']
exchange_func	33	13	39.39%	['fuzz_eval', 'fuzz_regexp', 'fuzz_compile']
js_os_poll	97	12	12.37%	['fuzz_compile', 'fuzz_eval']
JS_ExecutePendingJob	31	10	32.25%	['fuzz_compile', 'fuzz_eval']
JS_GetPropertyInternal	138	67	48.55%	['fuzz_compile', 'fuzz_eval']
JS_SetPropertyInternal	247	57	23.07%	['fuzz_compile', 'fuzz_eval']
JS_DefineProperty	262	89	33.96%	['fuzz_compile', 'fuzz_eval']
JS_GetOwnPropertyNamesInternal	180	74	41.11%	['fuzz_compile', 'fuzz_eval']
JS_GetOwnPropertyInternal	70	21	30.0%	['fuzz_compile', 'fuzz_eval']
JS_ToStringInternal	54	23	42.59%	['fuzz_compile', 'fuzz_eval']
js_call_c_function	112	51	45.53%	['fuzz_compile', 'fuzz_eval']
JS_CallInternal	2648	611	23.07%	['fuzz_compile', 'fuzz_eval']
js_host_resolve_imported_module	39	17	43.58%	['fuzz_compile', 'fuzz_eval']
js_default_module_normalize_name	46	8	17.39%	['fuzz_compile', 'fuzz_eval']
js_inner_module_linking	130	69	53.07%	['fuzz_compile', 'fuzz_eval']
JS_WriteObjectRec	137	25	18.24%	['fuzz_compile']
JS_WriteModule	44	17	38.63%	['fuzz_compile']
JS_ReadObjectRec	107	27	25.23%	['fuzz_compile']
JS_ReadModule	103	25	24.27%	['fuzz_compile']
js_string_define_own_property	32	11	34.37%	['fuzz_compile', 'fuzz_eval']
js_promise_resolve_function_call	41	19	46.34%	['fuzz_compile', 'fuzz_eval']
fulfill_or_reject_promise	32	15	46.87%	['fuzz_compile', 'fuzz_eval']
js_async_function_resume	45	20	44.44%	['fuzz_compile', 'fuzz_eval']
js_date_parse_isostring	54	12	22.22%	['fuzz_compile', 'fuzz_eval']
js_date_parse_otherstring	140	42	30.0%	['fuzz_compile', 'fuzz_eval']
next_token	417	214	51.31%	['fuzz_compile', 'fuzz_eval']
js_parse_string	120	60	50.0%	['fuzz_compile', 'fuzz_eval']
js_parse_postfix_expr	579	182	31.43%	['fuzz_compile', 'fuzz_eval']
js_parse_assign_expr2	236	46	19.49%	['fuzz_compile', 'fuzz_eval']
js_parse_logical_and_or	35	12	34.28%	['fuzz_compile', 'fuzz_eval']
js_parse_expr_binary	161	76	47.20%	['fuzz_compile', 'fuzz_eval']
js_parse_unary	129	39	30.23%	['fuzz_compile', 'fuzz_eval']
get_lvalue	121	55	45.45%	['fuzz_compile', 'fuzz_eval']
put_lvalue	109	35	32.11%	['fuzz_compile', 'fuzz_eval']
js_parse_import	125	36	28.79%	['fuzz_compile', 'fuzz_eval']
js_parse_statement_or_decl	627	99	15.78%	['fuzz_compile', 'fuzz_eval']
emit_return	68	17	25.0%	['fuzz_compile', 'fuzz_eval']
resolve_variables	309	137	44.33%	['fuzz_compile', 'fuzz_eval']
resolve_scope_var	425	176	41.41%	['fuzz_compile', 'fuzz_eval']
resolve_labels	776	311	40.07%	['fuzz_compile', 'fuzz_eval']
compute_stack_size	180	96	53.33%	['fuzz_compile', 'fuzz_eval']
ss_check	33	17	51.51%	['fuzz_compile', 'fuzz_eval']
unicode_to_utf8	32	16	50.0%	['fuzz_eval', 'fuzz_regexp', 'fuzz_compile']
js_dtoa_max_len	39	15	38.46%	['fuzz_compile', 'fuzz_eval']
js_dtoa	172	29	16.86%	['fuzz_compile', 'fuzz_eval']
lre_parse_escape	108	39	36.11%	['fuzz_eval', 'fuzz_regexp', 'fuzz_compile']
JS_HasProperty	37	20	54.05%	['fuzz_compile', 'fuzz_eval']
JS_GetPropertyValue	69	26	37.68%	['fuzz_compile', 'fuzz_eval']
delete_property	83	35	42.16%	['fuzz_compile', 'fuzz_eval']
JS_ToBoolFree	59	25	42.37%	['fuzz_compile', 'fuzz_eval']
JS_ToPrimitiveFree	69	34	49.27%	['fuzz_compile', 'fuzz_eval']
JS_ToInt64SatFree	38	13	34.21%	['fuzz_compile', 'fuzz_eval']
js_for_in_next	80	27	33.75%	['fuzz_compile', 'fuzz_eval']
js_for_in_prepare_prototype_chain_enum	52	23	44.23%	['fuzz_compile', 'fuzz_eval']
JS_GetIterator	31	12	38.70%	['fuzz_compile', 'fuzz_eval']
JS_IteratorNext2	31	17	54.83%	['fuzz_compile', 'fuzz_eval']
JS_ConcatString	72	19	26.38%	['fuzz_compile', 'fuzz_eval']
js_add_slow	103	22	21.35%	['fuzz_compile', 'fuzz_eval']
js_binary_arith_slow	178	35	19.66%	['fuzz_compile', 'fuzz_eval']
js_unary_arith_slow	134	27	20.14%	['fuzz_compile', 'fuzz_eval']
js_binary_logic_slow	153	28	18.30%	['fuzz_compile', 'fuzz_eval']
JS_CallConstructorInternal	40	15	37.5%	['fuzz_compile', 'fuzz_eval']
JS_ToObject	46	16	34.78%	['fuzz_compile', 'fuzz_eval']
js_compile_regexp	69	37	53.62%	['fuzz_compile', 'fuzz_eval']
js_regexp_constructor	78	27	34.61%	['fuzz_compile', 'fuzz_eval']
js_regexp_exec	196	101	51.53%	['fuzz_eval']
define_var	112	43	38.39%	['fuzz_eval']
js_parse_regexp	100	44	44.0%	['fuzz_eval']
js_parse_destructuring_element	403	84	20.84%	['fuzz_eval']
js_parse_property_name	106	19	17.92%	['fuzz_eval']
js_define_var	34	14	41.17%	['fuzz_eval']
js_array_join	50	27	54.0%	['fuzz_eval']
js_function_toString	38	10	26.31%	['fuzz_eval']

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/quickjs/./quickjs.h	['fuzz_compile', 'fuzz_eval']	[]
/src/quickjs/libregexp.c	['fuzz_regexp', 'fuzz_compile', 'fuzz_eval']	['fuzz_regexp', 'fuzz_compile', 'fuzz_eval']
/src/quickjs/./list.h	['fuzz_compile', 'fuzz_eval']	[]
/src/quickjs/./libunicode.h	['fuzz_regexp', 'fuzz_compile', 'fuzz_eval']	[]
/src/quickjs/quickjs.c	['fuzz_compile', 'fuzz_eval']	['fuzz_compile', 'fuzz_eval']
/src/quickjs/./cutils.h	['fuzz_regexp', 'fuzz_compile', 'fuzz_eval']	[]
/src/quickjs/cutils.c	['fuzz_regexp', 'fuzz_compile', 'fuzz_eval']	['fuzz_regexp', 'fuzz_compile', 'fuzz_eval']
/src/quickjs/quickjs-libc.c	['fuzz_compile', 'fuzz_eval']	['fuzz_compile', 'fuzz_eval']
/src/quickjs/dtoa.c	['fuzz_compile', 'fuzz_eval']	['fuzz_compile', 'fuzz_eval']
/src/quickjs/libunicode.c	['fuzz_regexp', 'fuzz_compile', 'fuzz_eval']	['fuzz_regexp', 'fuzz_eval']
/src/quickjs/fuzz/fuzz_compile.c	['fuzz_compile']	['fuzz_compile']
/src/quickjs/fuzz/fuzz_common.c	['fuzz_compile', 'fuzz_eval']	['fuzz_compile', 'fuzz_eval']
/src/quickjs/fuzz/fuzz_eval.c	['fuzz_eval']	['fuzz_eval']
/src/quickjs/fuzz/fuzz_regexp.c	['fuzz_regexp']	['fuzz_regexp']

Directories in report

Directory
/src/quickjs/fuzz/
/src/quickjs/./
/src/quickjs/