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.
11,107 Commits 188 Branches 0 Tags 127 MiB
Shell 27.3%
Python 19.3%
Dockerfile 17.4%
Java 17.1%
C 7.2%
Other 11.5%
Go to file
Kevin Backhouse 7f19f533e9
Delete ruby configuration (#12715) 
I added this project directory in #7820, but it generated quite a lot of
false positive results because the Ruby interpreter does a lot of weird
memory management stuff that doesn't interact well with ASAN. Due to the
false positives, the maintainers of https://github.com/ruby/ruby ignored
all of the results which led to some genuine bugs not getting fixed
before the 90-day deadline.

The build has been failing for a while now. Given the history, I don't
think it's worth trying to fix it, so I propose to delete this project.
 		2024-11-21 10:03:54 +11: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 build(deps-dev): bump rexml from 3.3.3 to 3.3.6 in /docs in the bundler group (#12515) 2024-09-19 09:10:34 -04:00
infra Build in stages to shed 9gb from the jvm base builder image (#12649) 2024-11-15 08:42:44 -08:00
projects Delete ruby configuration (#12715) 2024-11-21 10:03:54 +11: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 Add IntelliJ IDEA files to `.gitignore` (#12311) 2024-08-07 21:37:24 +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 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