Bug: 141203588

Clone this repo:
  1. db27988 Upgrade oss-fuzz to 1a87da68c870ce09ab6ffac30589da12e7ff6a8d by Haibo Huang · 3 weeks ago master android-r-preview-1
  2. 1a87da6 [cifuzz] - commit and pull request hook functionality (#3310) by Leo Neat · 3 weeks ago
  3. c2fa07a wasmtime: Enable debuginfo/frame pointers (#3314) by Alex Crichton · 3 weeks ago
  4. f2588ea Moving execute to utils.py (#3313) by Leo Neat · 3 weeks ago
  5. 7751ab5 [infra] Introduce "language" attribute in the project.yaml (#3297). (#3299) by Max Moroz · 3 weeks ago

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 and AFL 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.


OSS-Fuzz process diagram


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


As of January 2020, OSS-Fuzz has found over 16,000 bugs in 250 open source projects.

Blog posts