Bug: 141203588

Clone this repo:
  1. f53e077 Upgrade oss-fuzz to 167aec47bf047e3b3ccf01c5e4e3030144e86eea by Haibo Huang · 2 weeks ago master
  2. 167aec4 Add to maintainers for NATS (#4921) by Waldemar Quevedo · 2 weeks ago
  3. 33c867b serenity: Add myself and the mailing list to the cc list. (#4915) by Brian Gianforcaro · 2 weeks ago
  4. 6f19f3a [pyyaml] Initial integration. (#4717) by DavidKorczynski · 2 weeks ago
  5. c79f26d [valijson] Initial integration (#4854) by AdamKorcz · 2 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 and the OpenSSF, 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, Go and Python 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 2021, OSS-Fuzz has found over 25,000 bugs in 375 open source projects.

Blog posts