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.
7,044 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
DRC 5cc77a3fde
[libjpeg-turbo] Fuzz multiple code branches (#7528) 
libjpeg-turbo uses a stable mainline branch model, so the main branch is
always stable and feeds into the current release series.  The next-gen
evolving release series is developed in the dev branch, and bug fixes
are cherry-picked into stable branches for past release series.

It is desirable to fuzz the dev branch to ensure that bugs are caught
before the evolving code is merged down into main (which generally
occurs in conjunction with a beta release) and also to allow for the
fuzzers themselves to evolve along with the libjpeg-turbo feature set.
It is also desirable to fuzz the stable branch from the most recent
release series (2.0.x at the moment) to ensure that the same quality is
maintained from when that code occupied the main branch.

Note that both the Dockerfile and multi-branch build script included in
this commit accommodate the fact that the dev branch may not exist.  The
dev branch will not exist between the time that the current release
series enters beta and the first feature for the next-gen release series
is developed.

Closes #7479
 		2022-04-08 11:25:53 -04:00
.github build(deps): bump actions/setup-python from 2 to 3 (#7438) 2022-03-24 13:29:23 -04:00
docs Update new_project_guide.md (#7477) 2022-03-30 10:43:25 -04:00
infra Increase builds status timeout. (#7530) 2022-04-08 15:10:38 +10:00
projects [libjpeg-turbo] Fuzz multiple code branches (#7528) 2022-04-08 11:25:53 -04: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