Etusivu Tutki Apua
Kirjaudu sisään
thomas
/
open62541
Tarkkaile 1
Äänestä 0
Fork 0
Tiedostot Ongelmat 0 Pull-pyynnöt 0 Wiki
Puu: fb4a98f655
Branchit Tagit
open62541
/
tests
/
fuzz
Julius Pfrommer fb4a98f655 JSON: Switch to another base64 implementation after oss-fuzz problems 5 vuotta sitten
..
fuzz_binary_message_corpus 9009bd61f2 Fuzz: Regenerate corpus 6 vuotta sitten
fuzz_json 887ebf842c JSON: Add encoding/decoding fuzzing 5 vuotta sitten
CMakeLists.txt f19a6a1839 Stack: Correct include for architecture related headers 5 vuotta sitten
README.md a798be865b Fuzz: Add check_build script to verify successful build 5 vuotta sitten
check_build.sh a798be865b Fuzz: Add check_build script to verify successful build 5 vuotta sitten
corpus_generator.c 6fe8453249 Untabify 5 vuotta sitten
custom_memory_manager.c 6fe8453249 Untabify 5 vuotta sitten
custom_memory_manager.h c9c818868f Move header files to a more unix-like structure 5 vuotta sitten
fuzz_binary_decode.cc 63f3653ff1 Additional header cleanup and consistent name of ns generated files 5 vuotta sitten
fuzz_binary_message.cc fd08d012d9 Server: Initialize the config in the server 5 vuotta sitten
fuzz_binary_message.options 9fb0204cb2 Fuzz: Correct path to dicts 6 vuotta sitten
fuzz_binary_message_header.dict 9fb0204cb2 Fuzz: Correct path to dicts 6 vuotta sitten
fuzz_json_decode.cc dee5006b3d Fuzzer: Correct include for json fuzz 5 vuotta sitten
fuzz_json_decode_encode.cc fb4a98f655 JSON: Switch to another base64 implementation after oss-fuzz problems 5 vuotta sitten
fuzz_src_ua_util.cc 63f3653ff1 Additional header cleanup and consistent name of ns generated files 5 vuotta sitten
fuzz_src_ua_util.options 9fb0204cb2 Fuzz: Correct path to dicts 6 vuotta sitten
fuzz_src_ua_util_endpoints.dict 9fb0204cb2 Fuzz: Correct path to dicts 6 vuotta sitten
generate_corpus.sh 9009bd61f2 Fuzz: Regenerate corpus 6 vuotta sitten
oss-fuzz-copy.sh 660165267e Fix oss fuzz copy 7 vuotta sitten
ua_debug_dump_pkgs_file.c 4ff617ffed Fuzz: Fix a warning for snprintf overrun 5 vuotta sitten

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.