OSS-Fuzz - continuous fuzzing for open source software.
Go to file
Amol Grover 70c5678c62 Fix hyperlink markdown (#2926) 2019-10-08 10:48:41 -07:00
docs Fix typo 2019-09-24 16:25:00 -07:00
infra Add scripts to bisect clang commits that introduced regressions (#2849) 2019-10-03 15:35:31 -07:00
projects Add some more CCs for proxygen (#2925) 2019-10-08 08:57:34 -07:00
.gitignore [infra] replacing wget with ADD where possible 2016-12-28 14:09:09 -08:00
.travis.yml don't use travis_wait (#2867) 2019-09-20 11:24:02 -07:00
CONTRIBUTING.md Fix hyperlink markdown (#2926) 2019-10-08 10:48:41 -07:00
LICENSE Create LICENSE 2016-10-03 12:24:25 -07:00
README.md Document i386 fuzzing (#2704) 2019-08-19 14:07:33 -07:00
oss-fuzz.iml Add jekyll generator for docs. (#2660) 2019-08-06 13:29:19 -07:00

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, 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.

Overview

OSS-Fuzz process diagram

Documentation

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

Trophies

As of August 2019, OSS-Fuzz has found over 14,000 bugs in 200 open source projects.

Blog posts