High level conclusions

Reachability and coverage overview

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.

Fuzzer: crypt2_load_ondisk_fuzz

Call tree

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Runtime coverage analysis

Files reached

Fuzzer: crypt2_load_fuzz

Call tree

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Runtime coverage analysis

Files reached

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.

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

All functions overview

If you implement fuzzers for these functions, the status of all functions in the project will be:

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.

tests/fuzz/crypt2_load_ondisk_fuzz.cc

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=['isINTEGRITY', '_crypt_load_fvault2', 'crypt_free_volume_key', 'crypt_log', 'LLVMFuzzerTestOneInput', 'crypt_volume_key_get_key', 'crypt_free', 'isFVAULT2', 'BITLK_read_sb']

tests/fuzz/crypt2_load_fuzz.cc

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=['hdr_update_copy_for_rollback', 'crypt_set_null_type', 'crypt_random_get', 'json_segment_type', 'validate_json_uint32', 'json_object_copy', 'device_check_size', 'LLVMFuzzerTestOneInput', 'crypt_free', 'device_open_locked']

This section shows analysis of runtime coverage data.

Complex functions with low coverage

New fuzzers

The below fuzzers are templates and suggestions for how to target the set of optimal functions above

utils_reencrypt.c

#include "ada_fuzz_header.h"

int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
  af_safe_gb_init(data, size);

  /* target reencrypt */
  int new_var0 = ada_safe_get_int();
  char **new_var1 = af_get_double_char_p();
  reencrypt(new_var0, new_var1);

  af_safe_gb_cleanup();
}

setup.c

#include "ada_fuzz_header.h"

int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
  af_safe_gb_init(data, size);

  /* target _activate_reencrypt_device_by_vk */
  structcrypt_device* new_var2 = calloc(sizeof(structcrypt_device), 1);
  structluks2_hdr* new_var3 = calloc(sizeof(structluks2_hdr), 1);
  char *new_var4 = ada_safe_get_char_p();
  structvolume_key* new_var5 = calloc(sizeof(structvolume_key), 1);
  UNKNOWN_TYPE unknown_6;
  _activate_reencrypt_device_by_vk(new_var2, new_var3, new_var4, new_var5, unknown_6);

  /* target crypt_convert */
  structcrypt_device* new_var18 = calloc(sizeof(structcrypt_device), 1);
  char *new_var19 = ada_safe_get_char_p();
  UNKNOWN_TYPE unknown_20;
  crypt_convert(new_var18, new_var19, unknown_20);

  /* target _crypt_format */
  structcrypt_device* new_var30 = calloc(sizeof(structcrypt_device), 1);
  char *new_var31 = ada_safe_get_char_p();
  char *new_var32 = ada_safe_get_char_p();
  char *new_var33 = ada_safe_get_char_p();
  char *new_var34 = ada_safe_get_char_p();
  char *new_var35 = ada_safe_get_char_p();
  UNKNOWN_TYPE unknown_36;
  UNKNOWN_TYPE unknown_37;
  UNKNOWN_TYPE unknown_38;
  _crypt_format(new_var30, new_var31, new_var32, new_var33, new_var34, new_var35, unknown_36, unknown_37, unknown_38);

  af_safe_gb_cleanup();
}

luks2_reencrypt.c

#include "ada_fuzz_header.h"

int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
  af_safe_gb_init(data, size);

  /* target reencrypt_init */
  structcrypt_device* new_var7 = calloc(sizeof(structcrypt_device), 1);
  char *new_var8 = ada_safe_get_char_p();
  structluks2_hdr* new_var9 = calloc(sizeof(structluks2_hdr), 1);
  structcrypt_keyslot_context* new_var10 = calloc(sizeof(structcrypt_keyslot_context), 1);
  structcrypt_keyslot_context* new_var11 = calloc(sizeof(structcrypt_keyslot_context), 1);
  int new_var12 = ada_safe_get_int();
  int new_var13 = ada_safe_get_int();
  char *new_var14 = ada_safe_get_char_p();
  char *new_var15 = ada_safe_get_char_p();
  structcrypt_params_reencrypt* new_var16 = calloc(sizeof(structcrypt_params_reencrypt), 1);
  UNKNOWN_TYPE unknown_17;
  reencrypt_init(new_var7, new_var8, new_var9, new_var10, new_var11, new_var12, new_var13, new_var14, new_var15, new_var16, unknown_17);

  /* target reencrypt_step */
  structcrypt_device* new_var25 = calloc(sizeof(structcrypt_device), 1);
  structluks2_hdr* new_var26 = calloc(sizeof(structluks2_hdr), 1);
  structluks2_reencrypt* new_var27 = calloc(sizeof(structluks2_reencrypt), 1);
  UNKNOWN_TYPE unknown_28;
  UNKNOWN_TYPE unknown_29;
  reencrypt_step(new_var25, new_var26, new_var27, unknown_28, unknown_29);

  af_safe_gb_cleanup();
}

argon2.c

#include "ada_fuzz_header.h"

int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
  af_safe_gb_init(data, size);

  /* target argon2_verify */
  char *new_var21 = ada_safe_get_char_p();
  UNKNOWN_TYPE unknown_22;
  UNKNOWN_TYPE unknown_23;
  UNKNOWN_TYPE unknown_24;
  argon2_verify(new_var21, unknown_22, unknown_23, unknown_24);

  af_safe_gb_cleanup();
}

Files in report

Directories in report

This section shows a list of 3rd party function calls and their relative coverage information. By static analysis of the target project code, all of the 3rd party function call and their caller information, including the source file and line number that initiate the call are captured. The caller source code file and line number are shown in column 2 while column 1 is the function name of the 3rd party function call. Each occurrent of the 3rd party function call will occuply a separate row. Column 3 of each row indicate if the 3rd party call in the source file line is unreachable. Column 4 lists all fuzzers that have covered that particular system call in that specific location (source file and line)during their dynamic fuzzing.

Function in each files in report