Stefan Profanter 000b2a95c7 ci(fuzz): Error if tcp fuzzing can not be started vor 5 Jahren
..
fuzz_binary_message_corpus 7967cb3908 ci: Correctly name fuzz corpus to avoid name clash vor 5 Jahren
fuzz_json 887ebf842c JSON: Add encoding/decoding fuzzing vor 6 Jahren
CMakeLists.txt 0f1192c99a ci(fuzz): Add fuzzing for base64 encoding and decoding vor 5 Jahren
README.md a798be865b Fuzz: Add check_build script to verify successful build vor 5 Jahren
check_build.sh a798be865b Fuzz: Add check_build script to verify successful build vor 5 Jahren
corpus_generator.c 6fe8453249 Untabify vor 5 Jahren
custom_memory_manager.c e1c93c17cd fix: Mute custom memory manager if address entry not found vor 5 Jahren
custom_memory_manager.h c9c818868f Move header files to a more unix-like structure vor 5 Jahren
fuzz_base64_decode.cc 0f1192c99a ci(fuzz): Add fuzzing for base64 encoding and decoding vor 5 Jahren
fuzz_base64_encode.cc 0f1192c99a ci(fuzz): Add fuzzing for base64 encoding and decoding vor 5 Jahren
fuzz_binary_decode.cc cdd7abc6a6 ci(fuzz): Add author to license header vor 5 Jahren
fuzz_binary_message.cc cdd7abc6a6 ci(fuzz): Add author to license header vor 5 Jahren
fuzz_binary_message.options 9fb0204cb2 Fuzz: Correct path to dicts vor 6 Jahren
fuzz_binary_message_header.dict 9fb0204cb2 Fuzz: Correct path to dicts vor 6 Jahren
fuzz_json_decode.cc dee5006b3d Fuzzer: Correct include for json fuzz vor 5 Jahren
fuzz_json_decode_encode.cc fb4a98f655 JSON: Switch to another base64 implementation after oss-fuzz problems vor 5 Jahren
fuzz_src_ua_util.cc cdd7abc6a6 ci(fuzz): Add author to license header vor 5 Jahren
fuzz_src_ua_util.options 9fb0204cb2 Fuzz: Correct path to dicts vor 6 Jahren
fuzz_src_ua_util_endpoints.dict 9fb0204cb2 Fuzz: Correct path to dicts vor 6 Jahren
fuzz_tcp_message.cc 000b2a95c7 ci(fuzz): Error if tcp fuzzing can not be started vor 5 Jahren
generate_corpus.sh 4e7b4b342a ci: Update corpus for fuzzing vor 5 Jahren
oss-fuzz-copy.sh 6cff3c2c66 ci: Add tcp_fuzz_message fuzzer vor 5 Jahren
ua_debug_dump_pkgs_file.c cdd7abc6a6 ci(fuzz): Add author to license header vor 5 Jahren

README.md

I Can haz fuzz

open62541 is continuously tested with the awesome oss-fuzz project from Google: https://github.com/google/oss-fuzz

Currently tested is processing of binary messages and encoding/decoding of binary encoded data.

Reproduce locally

Reproduce build failure

You can just execute the script under tests/fuzz/check_build.sh, which does the following:

# clone oss-fuzz repo
cd oss-fuzz
# Change $OPEN62541_DIR to your local checkout of open62541
python infra/helper.py build_fuzzers --sanitizer address open62541 $OPEN62541_DIR && python infra/helper.py check_build --sanitizer address open62541

Reproduce issues

Download the testcase file and store it e.g. in your Download folder.

# clone oss-fuzz repo
cd oss-fuzz
# Change $OPEN62541_DIR to your local checkout of open62541
# And change $DOWNLOADS to your download location
python infra/helper.py build_fuzzers --sanitizer address open62541 $OPEN62541_DIR && python infra/helper.py reproduce open62541 fuzz_binary_decode $DOWNLOADS/clusterfuzz-testcase-minimized-fuzz_binary_decode-5686300273803264

Status

Update the corpus

To update the current corpus used for fuzzing you need to follow these steps. It will execute all the unit tests, dump the received data packages to a directory and then update and merge the corpus.

  1. The script will create two directories: open62541/build_fuzz and open62541/build_corpus. Make sure that these directories are not existing or do not contain any important data.

  2. Run the generate script:

open62541/tests/fuzz/generate_corpus.sh

This script will build all the unit tests, dump the packages and then merge the current corpus with the new packages.

  1. If there is new coverage with the generated data there will be new files in the directory:

open62541/fuzz/fuzz_binary_message_corpus/generated

Commit the new files and then you can delete the build directories created in step 1.