Rooba
/
oss-fuzz
mirror of https://github.com/google/oss-fuzz.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity
OSS-Fuzz - continuous fuzzing for open source software.
6,924 Commits 189 Branches 0 Tags 109 MiB
Shell 27.3%
Python 19.2%
Dockerfile 17.5%
Java 17.1%
C 7.2%
Other 11.5%
Go to file
Yong Tang 0aac0529ad
Update coredns with additional auto_ccs (#7364) 
Hi, I am a coredns maintainer (see https://github.com/coredns/coredns/blob/master/CODEOWNERS)
and I used to receive oss-fuzz issues through `security@coredns.io`.
Recently I tried to address some of the security issues received, but then I noticed that
I can only access the list with google login. Since security@coredns.io
is a mailing list it will not be possible to login.
So adding my email to this list.

Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
 		2022-03-07 18:52:38 +00:00
.github Use libClusterFuzz for CIFuzz fuzzing and pruning. (#6375) 2021-09-13 12:16:13 +10:00
docs Bump nokogiri from 1.12.5 to 1.13.3 in /docs (#7334) 2022-02-27 11:39:44 -05:00
infra handle wildcard label applying to all fuzz targets in a project (#7359) 2022-03-04 14:59:08 +11:00
projects Update coredns with additional auto_ccs (#7364) 2022-03-07 18:52:38 +00:00
.dockerignore [ClusterFuzzLite] Support GCB and gsutil/gcs as filestore. (#6629) 2021-10-27 10:00:04 -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 [ClusterFuzzLite] Support local runs (#6987) 2022-01-19 17:24:47 -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 and Java/JVM 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 January 2022, OSS-Fuzz has found over 36,000 bugs in 550 open source projects.

Blog posts