Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / oss-fuzz / cfb18fbea730ea9e0b2a5e814e74b7ddf1f8e35a
commitcfb18fbea730ea9e0b2a5e814e74b7ddf1f8e35a[log] [tgz]
authorAbhishek Arya <inferno@chromium.org>Wed Jul 15 09:46:24 2020 -0700
committerGitHub <noreply@github.com>Wed Jul 15 09:46:24 2020 -0700
tree4b93710d3290db07845f339392e0b82104150d49
parent26dcd1ac18a54d5c5e2a6a5731095c1492956feb [diff]
CI fix. (#4139)
5 files changed
tree: 4b93710d3290db07845f339392e0b82104150d49
  1. .github/
  2. docs/
  3. infra/
  4. projects/
  5. .gitignore
  6. .pylintrc
  7. .style.yapf
  8. CONTRIBUTING.md
  9. LICENSE
  10. oss-fuzz.iml
  11. README.md
README.md

OSS-Fuzz: Continuous Fuzzing for Open Source Software

Fuzz testing is a well-known technique for uncovering programming errors in software. Many of these detectable errors, like buffer overflow, can have serious security implications. Google has found thousands of security vulnerabilities and stability bugs by deploying guided in-process fuzzing of Chrome components, and we now want to share that service with the open source community.

In cooperation with the Core Infrastructure Initiative, OSS-Fuzz aims to make common open source software more secure and stable by combining modern fuzzing techniques with scalable, distributed execution.

We support the libFuzzer, AFL and Honggfuzz fuzzing engines in combination with Sanitizers, as well as ClusterFuzz, a distributed fuzzer execution environment and reporting tool.

Currently, OSS-Fuzz supports C/C++, Rust, and Go code. Other languages supported by LLVM may work too. OSS-Fuzz supports fuzzing x86_64 and i386 builds.

Overview

OSS-Fuzz process diagram

Documentation

Read our detailed documentation to learn how to use OSS-Fuzz.

Trophies

As of June 2020, OSS-Fuzz has found over 20,000 bugs in 300 open source projects.

Blog posts