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.
10,686 Commits 187 Branches 0 Tags 132 MiB
Shell 27.2%
Python 19.3%
Dockerfile 17.5%
Java 17.1%
C 7.2%
Other 11.6%
Go to file
Andy Ross 4fa716901b
sound-open-firmware: SOF integration has bitrotten. Revive it. (#12135) 
This doesn't get as much attention as it should, fixups to recover
oss-fuzz output:

1. The Zephyr SDK 0.16.1 probably still works from a year ago, but the
fetch URL scheme changed so we'll never know. Implement some horrible
hackery to extract the "latest" version of the SDK at docker time so
(absent more changes to the releases URLs) we stay current.

2. The build.sh was my original hack with manual kconfig settings, which
have skewed vs. the app as it evolved and don't build anymore. SOF has
fuzzing implemented as a first class tool now (and even run it in their
CI), so just use the official script which we can rely on being
maintained.

Signed-off-by: Andy Ross <andyross@google.com>
 		2024-07-02 08:29:43 -04: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 pr_helper: Use process.env instead of string interpolation (#11960) 2024-05-15 23:37:16 -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 [NFC] Simplify clang build script. (#11923) 2024-07-02 08:26:40 -04:00
projects sound-open-firmware: SOF integration has bitrotten. Revive it. (#12135) 2024-07-02 08:29:43 -04: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 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
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 Create LICENSE 2016-10-03 12:24:25 -07:00
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

OSS-Fuzz process diagram

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