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.
5,320 Commits 195 Branches 0 Tags 125 MiB
Shell 27.3%
Python 19.2%
Dockerfile 17.4%
Java 17%
C 7.2%
Other 11.7%
Go to file
Andrea Fioraldi f682792936
[openjpeg] Release cmake build type (#5209) 
Seems that some bugs in openjpeg can be triggered only in release mode.
More specifically, I was trying to reproduce https://github.com/uclouvain/openjpeg/issues/1228 using the OSS-Fuzz harness and I failed.
I figured out that the bug is indeed reachable by the harness, but can be uncovered only in Release mode, otherwise, an assertion error blocks it.
I guess that they use assertions only in Debug mode (WTF) and remove them in Release.
So, IMO openjpeg should be fuzzed in Release mode as the configuration used in production is the one relevant for security.
 		2021-02-18 10:17:18 -08:00
.github/workflows [infra] Improve test speed (#5118) 2021-02-05 06:10:42 -08:00
docs [CIFuzz] Fix handling of sanitizer artifacts (#5182) 2021-02-18 09:57:34 -08:00
infra [CIFuzz] Fix handling of sanitizer artifacts (#5182) 2021-02-18 09:57:34 -08:00
projects [openjpeg] Release cmake build type (#5209) 2021-02-18 10:17:18 -08:00
.dockerignore Reland 55d9a81. (#4269) 2020-08-06 14:33:08 -07: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 Fix missed AFL++ changes in README.md 2021-01-26 15:29:02 -08: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.

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 and Python 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 2021, OSS-Fuzz has found over 25,000 bugs in 375 open source projects.

Blog posts