OSS-Fuzz - continuous fuzzing for open source software.
Go to file
jonathanmetzman 55d9a81cd7
[CIFuzz] Allow supplying a manual source checkout (#4250)
Make CIFuzz building accept an env var `MANUAL_SRC_PATH` that points to a manually prepared checkout of the project-under-tests's source code. This allows projects like Skia which are not on OSS-Fuzz and/or need to make changes to the repo after checking out the right commit to use CIFuzz.
Note that for now we aren't supporting this in GitHub, so projects that need to modify the source after checkout can't use it until
we do support it.

Also, use the local copy of OSS-Fuzz when building cifuzz-base instead of cloning it from GitHub. This makes local debugging/development much easier since it allows one to use CIFuzz with local changes.
2020-08-05 18:45:12 -07:00
.github/workflows CI fix. (#4139) 2020-07-15 09:46:24 -07:00
docs Updating documentation to reflect new feature custom build frequency (#4235) 2020-08-03 10:43:35 -07:00
infra [CIFuzz] Allow supplying a manual source checkout (#4250) 2020-08-05 18:45:12 -07:00
projects [vorbis] Use shallow clone (#4259) 2020-08-05 15:45:14 -07:00
.dockerignore [CIFuzz] Allow supplying a manual source checkout (#4250) 2020-08-05 18:45:12 -07:00
.gitignore Delete unnecessary files and fix format in some MD pages (#4115) 2020-07-16 15:27:29 -07:00
.pylintrc More build infra cleanup. (#4252) 2020-08-06 09:36:47 +10:00
.style.yapf [infra] Add presubmit script (#3196) 2020-01-10 10:19:42 -08:00
CONTRIBUTING.md Delete unnecessary files and fix format in some MD pages (#4115) 2020-07-16 15:27:29 -07:00
LICENSE Create LICENSE 2016-10-03 12:24:25 -07:00
README.md Delete unnecessary files and fix format in some MD pages (#4115) 2020-07-16 15:27:29 -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, 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, 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 June 2020, OSS-Fuzz has found over 20,000 bugs in 300 open source projects.

Blog posts