commit	c66a9d2b530ee8190761ba98689abb39e4ee98ac	[log] [tgz]
author	jonathanmetzman <31354670+jonathanmetzman@users.noreply.github.com>	Wed Sep 15 13:29:52 2021 -0700
committer	GitHub <noreply@github.com>	Wed Sep 15 20:29:52 2021 +0000
tree	6be822dade124b7b68f110a7a6df3f64644f2387
parent	dab5a9945b4a4170f0e824f6db682e9b3dd33898 [diff]

tree: 6be822dade124b7b68f110a7a6df3f64644f2387

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 June 2021, OSS-Fuzz has found over 30,000 bugs in 500 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