OSS-Fuzz - continuous fuzzing for open source software.

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

Go to file

correctmost 0166f6a772 cilium: fix seed corpus placement (#12260 ) Files copied to /out during image creation seem to get hidden by a volume mounted at /out when building the fuzzers. Similar issues: - https://github.com/google/oss-fuzz/pull/12254 - https://github.com/google/oss-fuzz/pull/12250 - https://github.com/google/oss-fuzz/pull/12259		2024-07-22 13:38:16 +01:00
.allstar	Opt out of allstar binary artifacts check (#7816 )	2022-06-08 09:37:08 -04:00
.clusterfuzzlite	ClusterFuzzLite: fix fuzzer (#11649 )	2024-02-28 22:32:52 -05:00
.github	Update several github action to node20 verisons (#12048 )	2024-07-03 23:44:20 -04:00
docs	doc: add rust to list of languages that support llvm-cov arguments (#12127 )	2024-06-26 16:05:49 -04:00
infra	helper: fix coverage extra args reading (#12255 )	2024-07-20 17:55:06 +01:00
projects	cilium: fix seed corpus placement (#12260 )	2024-07-22 13:38:16 +01:00
tools/vscode-extension	vscode: project gen: adjust CXXFLAGS for cpp builds (#11412 )	2023-12-27 11:06:35 +00: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	infra: add vscode extension poc (#10592 )	2023-08-28 10:51:45 +01:00
.pylintrc	Dont allow unsued globals and allow fp (#12190 )	2024-07-09 12:26:06 -04:00
.style.yapf	[infra] Add presubmit script (#3196 )	2020-01-10 10:19:42 -08:00
CITATION.cff	Update CITATION.cff	2024-05-01 11:54:21 -04:00
CONTRIBUTING.md	Delete unnecessary files and fix format in some MD pages (#4115 )	2020-07-16 15:27:29 -07:00
LICENSE	…
README.md	Update README.md (#11643 )	2024-02-29 13:06:10 -05: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 August 2023, OSS-Fuzz has helped identify and fix over 10,000 vulnerabilities and 36,000 bugs across 1,000 projects.

Blog posts

2023-08-16 - AI-Powered Fuzzing: Breaking the Bug Hunting Barrier
2023-02-01 - Taking the next step: OSS-Fuzz in 2023
2022-09-08 - Fuzzing beyond memory corruption: Finding broader classes of vulnerabilities automatically
2021-12-16 - Improving OSS-Fuzz and Jazzer to catch Log4Shell
2021-03-10 - Fuzzing Java in OSS-Fuzz
2020-12-07 - Improving open source security during the Google summer internship program
2020-10-09 - Fuzzing internships for Open Source Software
2018-11-06 - A New Chapter for OSS-Fuzz
2017-05-08 - OSS-Fuzz: Five months later, and rewarding projects
2016-12-01 - Announcing OSS-Fuzz: Continuous fuzzing for open source software