OSS-Fuzz - continuous fuzzing for open source software.

fuzzing fuzz-testing oss-fuzz security stability starred-google-repo starred-repo vulnerabilities

Go to file

jonathanmetzman e164f29e81 [cifuzz] remove test code. (#10181 ) Fix test code.		2023-04-27 14:26:15 -04:00
.allstar	Opt out of allstar binary artifacts check (#7816 )	2022-06-08 09:37:08 -04:00
.clusterfuzzlite	Fuzz OSS-Fuzz with Atheris and ClusterFuzzLite (#8985 )	2022-11-30 15:37:36 -05:00
.github	ci: Double free space from 30 GB to 60 GB (#9836 )	2023-03-02 14:07:26 -05:00
docs	doc: replace libfuzzer.info links with llvm.org (#10131 )	2023-04-24 11:35:51 +10:00
infra	[cifuzz] remove test code. (#10181 )	2023-04-27 14:26:15 -04:00
projects	[lua][waiting for upstream]: add new fuzzers (#10092 )	2023-04-27 10:15:29 -04:00
.dockerignore	[ClusterFuzzLite] Support GCB and gsutil/gcs as filestore. (#6629 )	2021-10-27 10:00:04 -04:00
.gitattributes	Add .gitattributes to specify LF as .sh line terminator (#7648 )	2022-05-02 10:12:06 -04:00
.gitignore	Improve CIFuzz tests (#4868 )	2020-12-18 10:37:56 -08:00
.pylintrc	Replace terms that are uninclusive. (#5045 )	2021-01-25 08:41:34 -08: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	Add missing blog posts (#9569 )	2023-02-03 01:51:08 +00: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 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. Projects that do not qualify for OSS-Fuzz (e.g. closed source) can run their own instances of ClusterFuzz or ClusterFuzzLite.

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, Java/JVM, and JavaScript code. Other languages supported by LLVM may work too. OSS-Fuzz supports fuzzing x86_64 and i386 builds.

Overview

Documentation

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

Trophies

As of February 2023, OSS-Fuzz has helped identify and fix over 8,900 vulnerabilities and 28,000 bugs across 850 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
2021-03-10 - Fuzzing Java in OSS-Fuzz
2021-12-16 - Improving OSS-Fuzz and Jazzer to catch Log4Shell
2022-09-08 - Fuzzing beyond memory corruption: Finding broader classes of vulnerabilities automatically
2023-02-01 - Taking the next step: OSS-Fuzz in 2023