Skip to content

Latest commit

 

History

History
50 lines (39 loc) · 2.89 KB

reproducing.md

File metadata and controls

50 lines (39 loc) · 2.89 KB
Raw

Reproducing OSS-Fuzz issues

You've been CC'ed on an OSS-Fuzz issue (examples), now what? Before attempting to fix the bug, you should be able to reliably reproduce it.

Every issue has a reproducer (aka "testcase") file attached. Download it. If the issue is not public, you will need to login using your Google account that the bug report CCs. This file contains the bytes that were fed to the Fuzz Target.

If you have already integrated the fuzz target with your build and test system, all you do is run:

./fuzz_target_binary $testcase_file_absolute_path

Depending on the nature of the bug, the fuzz target binary needs to be built with the appropriate sanitizer (e.g. if this is a buffer overflow, with AddressSanitizer).

If you are not sure how to build the fuzzer using the project's build system, you may also use Docker (how?, why?) commands to replicate the exact build steps used by OSS-Fuzz and then feed the reproducer input to the fuzz target.

  • Reproduce using latest OSS-Fuzz build:

    • 



docker run --rm -ti -v $testcase_file_absolute_path:/testcase ossfuzz/$project reproduce $fuzzer



It builds the fuzzer from the most recent successful OSS-Fuzz build (usually last night's sources)
and feeds the testcase file to the target function.


E.g. for libxml2 project with fuzzer named libxml2_xml_read_memory_fuzzer, it will be:

   
docker run --rm -ti -v ~/Downloads/testcase:/testcase ossfuzz/libxml2 reproduce libxml2_xml_read_memory_fuzzer
   


    

  • 

    Reproduce using local source checkout:
    
  
      docker run --rm -ti -v $local_source_checkout_dir:/src/$project \
                      -v $testcase_file_absolute_path:/testcase ossfuzz/$project reproduce $fuzzer
  
    

    This is essentially the previous command that additionally mounts local sources into the running container.
    

    • 

  • 

    Fix issue. Write a patch to fix the issue in your local checkout and then use the previous command to verify the fix (i.e. no crash occurred).
Use gdb if needed.
    

    • 

  • 

    Submit fix. Submit the fix in the project's repository. ClusterFuzz will automatically pick up the changes, recheck the testcase and will close the issue (in < 1 day).
    

    • 

  • 

    Improve fuzzing support. Consider improving fuzzing support in your project's build and test system.
    

    •