commit	a825726f27348619e814ddbd41d133cfa8d8600e	[log] [tgz]
author	Andrew Brown <andrew.brown@intel.com>	Mon Mar 29 12:10:23 2021 -0700
committer	GitHub <noreply@github.com>	Mon Mar 29 12:10:23 2021 -0700
tree	79e5231a52189bb1a82f6b3aad8b8d70cb52d621
parent	346ef66a268d0fa192becaf2730e7e3722ecd2a6 [diff]

tree: 79e5231a52189bb1a82f6b3aad8b8d70cb52d621

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 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, Python and Java/JVM 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 January 2021, OSS-Fuzz has found over 25,000 bugs in 375 open source projects.

Blog posts

2016-12-01 - Announcing OSS-Fuzz: Continuous fuzzing for open source software
2017-05-08 - OSS-Fuzz: Five months later, and rewarding projects
2018-11-06 - A New Chapter for OSS-Fuzz
2020-10-09 - Fuzzing internships for Open Source Software
2020-12-07 - Improving open source security during the Google summer internship program