Bug: 141203588

Clone this repo:
  1. 8c011a1 Upgrade oss-fuzz to 4e241e814080eac62a106931214cbd17275182cc am: 61804fe0f0 by Haibo Huang · 9 weeks ago master android-r-beta-2
  2. 61804fe Upgrade oss-fuzz to 4e241e814080eac62a106931214cbd17275182cc by Haibo Huang · 9 weeks ago
  3. 4e241e8 Update project.yaml (#3917) by Ingo Berg · 9 weeks ago
  4. e3e1174 [haproxy] Fix build failures. (#3884) by DavidKorczynski · 9 weeks ago
  5. 0f50310 [muparser] initial integration (#3814) by Zhicheng Cai · 9 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