Continuous Integration

OSS-Fuzz offersCIFuzz, a GitHub action/CI job that runs your fuzz targets on pull requests. This works similarly to running unit tests in CI. CIFuzz helps you find and fix bugs before they make it into your codebase. Currently, CIFuzz primarily supports projects hosted on GitHub. Non-OSS-Fuzz users can use CIFuzz with additional features throughClusterFuzzLite.

How it works

CIFuzz builds your project’s fuzzers from the source at a particular pull request or commit. Then CIFuzz runs the fuzzers for a short amount of time. If CIFuzz finds a crash, CIFuzz reports the stacktrace, makes the crashing input available for download and the CI test fails (red X).

If CIFuzz doesn’t find a crash during the allotted time, the CI test passes (green check). If CIFuzz finds a crash, it reports the crash only if both of following are true:

• The crash is reproducible (on the PR/commit build).
• The crash does not occur on older OSS-Fuzz builds. (If the crash does occur on older builds, then it was not introduced by the PR/commit being tested.)

If your project supportsOSS-Fuzz’s code coverage, CIFuzz only runs the fuzzers affected by a pull request/commit. Otherwise it will divide up the allotted fuzzing time (10 minutes by default) among all fuzzers in the project.

CIFuzz uses 30 day old/public regressions and corpora from OSS-Fuzz. This makes fuzzing more effective and gives you regression testing for free.

Requirements

1. Your project must be integrated with OSS-Fuzz.
2. Your project is hosted on GitHub.
3. Your repository needs to be cloned withgit in oss-fuzz Dockerfile (do not usego get or other methods)

Integrating into your repository

You can integrate CIFuzz into your project using the following steps:

1. Create a.github directory in the root of your project.
2. Create aworkflows directory inside of your.github directory.
3. Copy the examplecifuzz.yml file over from the OSS-Fuzz repository to theworkflows directory.
4. Change theoss-fuzz-project-name value incifuzz.yml fromexample to the name of your OSS-Fuzz project. It isvery important that you use your OSS-Fuzz project name which is case sensitive. This name is the name of your project’s subdirectory in theprojects directory of OSS-Fuzz.
5. Set the value offuzz-seconds. The longest time that the project maintainers are acceptable with should be used. This value should be at minimum 600 seconds and scale with project size.

Your directory structure should look like the following:

project|___ .github|    |____ workflows|          |____ cifuzz.yml|___ other-files

cifuzz.yml for an example project:

name:CIFuzzon:[pull_request]permissions:{}jobs:Fuzzing:runs-on:ubuntu-latestpermissions:security-events:writesteps:-name:Build Fuzzersid:builduses:google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@masterwith:oss-fuzz-project-name:'example'language:c++-name:Run Fuzzersuses:google/oss-fuzz/infra/cifuzz/actions/run_fuzzers@masterwith:oss-fuzz-project-name:'example'language:c++fuzz-seconds:600output-sarif:true-name:Upload Crashuses:actions/upload-artifact@v4if:failure() && steps.build.outcome == 'success'with:name:artifactspath:./out/artifacts-name:Upload Sarifif:always() && steps.build.outcome == 'success'uses:github/codeql-action/upload-sarif@v2with:# Path to SARIF file relative to the root of the repositorysarif_file:cifuzz-sarif/results.sarifcheckout_path:cifuzz-sarif

Optional configuration

Configurable Variables

language: (optional) The language your target program is written in. Defaults toc++. This should be the same as the value you set inproject.yaml. Seethis explanation for more details.

fuzz-seconds: Determines how long CIFuzz spends fuzzing your project in seconds. The default is 600 seconds. The GitHub Actions max run time is 21600 seconds (6 hours). This variable is only meaningful when supplied to therun_fuzzers action, not thebuild_fuzzers action.

dry-run: Determines if CIFuzz surfaces errors. The default value isfalse. When set totrue, CIFuzz will never report a failure even if it finds a crash in your project. This requires the user to manually check the logs for detected bugs. If dry run mode is desired, make sure to set the dry-run parameters in both theBuild Fuzzers andRun Fuzzers action step.

allowed-broken-targets-percentage: Can be set if you want to set a stricter limit for broken fuzz targets than OSS-Fuzz’s check_build. Most users should not set this. This value is only meaningful when supplied to therun_fuzzers action, not thebuild_fuzzers action.

sanitizer: Determines a sanitizer to build and run fuzz targets with. The choices are'address','memory' and'undefined'. The default is'address'. It is important to note that theBuild Fuzzers and theRun Fuzzers sanitizer field needs to be the same. To specify a list of sanitizers amatrix can be used. To use a sanitizer add it to the list of sanitizers in the matrix field below:

report-timeouts: Determines whether to report fails due to timeouts.

report-ooms: Determines whether to report fails due to OOM.

name:CIFuzzon:[pull_request]permissions:{}jobs:Fuzzing:runs-on:ubuntu-latestpermissions:security-events:writestrategy:fail-fast:falsematrix:sanitizer:[address,undefined,memory]steps:-name:Build Fuzzers (${{ matrix.sanitizer }})id:builduses:google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@masterwith:oss-fuzz-project-name:'example'language:c++sanitizer:${{ matrix.sanitizer }}-name:Run Fuzzers (${{ matrix.sanitizer }})uses:google/oss-fuzz/infra/cifuzz/actions/run_fuzzers@masterwith:oss-fuzz-project-name:'example'language:c++fuzz-seconds:600sanitizer:${{ matrix.sanitizer }}output-sarif:true-name:Upload Crashuses:actions/upload-artifact@v4if:steps.build.outcome == 'success'with:name:${{ matrix.sanitizer }}-artifactspath:./out/artifacts-name:Upload Sarifif:always() && steps.build.outcome == 'success'uses:github/codeql-action/upload-sarif@v2with:# Path to SARIF file relative to the root of the repositorysarif_file:cifuzz-sarif/results.sarifcheckout_path:cifuzz-sarif

Branches and paths

You can make CIFuzz trigger only on certain branches or paths by following the instructionshere. For example, the following code can used to trigger CIFuzz only on changes to C/C++ code residing on master and release branches:

name:CIFuzzon:pull_request:branches:-master-'releases/**'paths:-'**.c'-'**.cc'-'**.cpp'-'**.cxx'-'**.h'permissions:{}jobs:Fuzzing:runs-on:ubuntu-lateststeps:-name:Build Fuzzersid:builduses:google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@masterwith:oss-fuzz-project-name:'example'language:c++-name:Run Fuzzersuses:google/oss-fuzz/infra/cifuzz/actions/run_fuzzers@masterwith:oss-fuzz-project-name:'example'language:c++fuzz-seconds:600-name:Upload Crashuses:actions/upload-artifact@v4if:failure() && steps.build.outcome == 'success'with:name:artifactspath:./out/artifacts

You can checkout CIFuzz configs for OSS-Fuzz projects. Example -systemd,curl.

Understanding results

The results of CIFuzz can be found in two different places.

• Run fuzzers log:
  1. This log can be accessed in theactions tab of a CIFuzz integrated repo.
  2. Click on theCIFuzz button in the workflow selector on the left hand side.
  3. Click on the event triggered by your desired pull request.
  4. Click theFuzzing workflow.
  5. Select theRun Fuzzer drop down. It should show the timestamps and results from each of the fuzz targets.

• Artifacts: When the fuzzer crashes the input file that causes the crash is uploaded as an artifact. To download the artifact, do the following steps:
  1. Click on the summary from the run, as illustrated in the screenshot below:

1. Click on the artifact you wish to download from the summary page, as illustrated in the screenshot below:

Feedback/Questions/Issues

Create an issue inOSS-Fuzz if you have questions or any other feedback on CIFuzz.