OSS-Fuzz - continuous fuzzing for open source software.
Go to file
bungeman d83e3f543d
[freetype] Remove zlib and libpng dev packages. (#4597)
The upstream build of the fuzzer currently builds freetype --without-zlib
and --without-png so these are not needed. In addition, because of the
way these dependencies are used they must be built with the sanitizer in
order to detect interesting issues like CVE-2020-15999, where FreeType
may call into libpng incorrectly but it is libpng which actually does
the reads and writes. This has been proposed upstream at
https://github.com/freetype/freetype2-testing/pull/86 which uses
prefixes to ensure that the system symbols are never used, but it would
be beneficial to not have them available at all.
2020-11-04 11:01:18 -08:00
.github/workflows CI fix. (#4139) 2020-07-15 09:46:24 -07:00
docs [docs] Reproducing: clarify that reproduce command works only with libfuzzer (#4497). (#4504) 2020-10-05 12:53:37 -07:00
infra [CIFuzz] Don't assume fuzzer output is ASCII (#4537) 2020-10-19 10:10:22 -07:00
projects [freetype] Remove zlib and libpng dev packages. (#4597) 2020-11-04 11:01:18 -08:00
.dockerignore Reland 55d9a81. (#4269) 2020-08-06 14:33:08 -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