• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..--

.github/workflows/23-Nov-2023-152127

docs/23-Nov-2023-3,0152,336

infra/23-Nov-2023-18,39612,783

projects/23-Nov-2023-72,11151,796

.dockerignoreD23-Nov-2023103 1110

.gitignoreD23-Nov-202347 77

.pylintrcD23-Nov-202317.6 KiB587440

.style.yapfD23-Nov-2023101 65

Android.bpD23-Nov-20232 KiB5652

CONTRIBUTING.mdD23-Nov-20231.4 KiB2723

LICENSED23-Nov-202311.1 KiB202169

METADATAD23-Nov-2023405 2019

MODULE_LICENSE_APACHE2D23-Nov-20230

OWNERSD23-Nov-202361 43

README.mdD23-Nov-20233.3 KiB6549

README.md

1# OSS-Fuzz: Continuous Fuzzing for Open Source Software
2
3[Fuzz testing] is a well-known technique for uncovering programming errors in
4software. Many of these detectable errors, like [buffer overflow], can have
5serious security implications. Google has found [thousands] of security
6vulnerabilities and stability bugs by deploying [guided in-process fuzzing of
7Chrome components], and we now want to share that service with the open source
8community.
9
10[Fuzz testing]: https://en.wikipedia.org/wiki/Fuzz_testing
11[buffer overflow]: https://en.wikipedia.org/wiki/Buffer_overflow
12[thousands]: https://bugs.chromium.org/p/chromium/issues/list?q=label%3AStability-LibFuzzer%2CStability-AFL%20-status%3ADuplicate%2CWontFix&can=1
13[guided in-process fuzzing of Chrome components]: https://security.googleblog.com/2016/08/guided-in-process-fuzzing-of-chrome.html
14
15In cooperation with the [Core Infrastructure Initiative] and the [OpenSSF],
16OSS-Fuzz aims to make common open source software more secure and stable by
17combining modern fuzzing techniques with scalable, distributed execution.
18
19[Core Infrastructure Initiative]: https://www.coreinfrastructure.org/
20[OpenSSF]: https://www.openssf.org/
21
22We support the [libFuzzer], [AFL++], and [Honggfuzz] fuzzing engines in
23combination with [Sanitizers], as well as [ClusterFuzz], a distributed fuzzer
24execution environment and reporting tool.
25
26[libFuzzer]: https://llvm.org/docs/LibFuzzer.html
27[AFL++]: https://github.com/AFLplusplus/AFLplusplus
28[Honggfuzz]: https://github.com/google/honggfuzz
29[Sanitizers]: https://github.com/google/sanitizers
30[ClusterFuzz]: https://github.com/google/clusterfuzz
31
32Currently, OSS-Fuzz supports C/C++, Rust, Go, Python and Java/JVM code. Other languages
33supported by [LLVM] may work too. OSS-Fuzz supports fuzzing x86_64 and i386
34builds.
35
36[LLVM]: https://llvm.org
37
38## Overview
39![OSS-Fuzz process diagram](docs/images/process.png)
40
41## Documentation
42Read our [detailed documentation] to learn how to use OSS-Fuzz.
43
44[detailed documentation]: https://google.github.io/oss-fuzz
45
46## Trophies
47As of January 2021, OSS-Fuzz has found over [25,000] bugs in [375] open source
48projects.
49
50[25,000]: https://bugs.chromium.org/p/oss-fuzz/issues/list?q=-status%3AWontFix%2CDuplicate%20-component%3AInfra&can=1
51[375]: https://github.com/google/oss-fuzz/tree/master/projects
52
53## Blog posts
54* 2016-12-01 - [Announcing OSS-Fuzz: Continuous fuzzing for open source software]
55* 2017-05-08 - [OSS-Fuzz: Five months later, and rewarding projects]
56* 2018-11-06 - [A New Chapter for OSS-Fuzz]
57* 2020-10-09 - [Fuzzing internships for Open Source Software]
58* 2020-12-07 - [Improving open source security during the Google summer internship program]
59
60[Announcing OSS-Fuzz: Continuous fuzzing for open source software]: https://opensource.googleblog.com/2016/12/announcing-oss-fuzz-continuous-fuzzing.html
61[OSS-Fuzz: Five months later, and rewarding projects]: https://opensource.googleblog.com/2017/05/oss-fuzz-five-months-later-and.html
62[A New Chapter for OSS-Fuzz]: https://security.googleblog.com/2018/11/a-new-chapter-for-oss-fuzz.html
63[Fuzzing internships for Open Source Software]: https://security.googleblog.com/2020/10/fuzzing-internships-for-open-source.html
64[Improving open source security during the Google summer internship program]: https://security.googleblog.com/2020/12/improving-open-source-security-during.html
65