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.
4,077 Commits 188 Branches 0 Tags 128 MiB
Shell 27.3%
Python 19.3%
Dockerfile 17.4%
Java 17.1%
C 7.2%
Other 11.5%
Go to file
Sebastian Rasmussen e2e155fe0e
Update flags and enable new sanitizer (#3587) 
* [ghostscript] Replace deprecated flag by current flag.

In old versions of Ghostscript the flag -dPARANOIDSAFER did
more checks than -dSAFER did. In modern versions the two flags
are identical. Moreover the flag -dPARANOIDSAFER has been
deprecated for a long time, and may be removed in the future.

In Ghostscript 9.50 and later -dSAFER is the default, and does
not have to be specified. To be able to test older yet still
modern Ghostscript versions without problems -dSAFER is used.

* [ghostscript] Force enable banding while rendering.

Ghostscript uses the set resolution to determine if banding should be
enabled during rendering, or not. Under normal circumstances documents
are rendered at maybe 600 DPI, but to conserve memory while running in
OSS-fuzz 200 DPI is used (-r200x200). To still test the banding code
used under normal circumstances banding is force enabled.

Moreover BufferSpace is used to determine the band height and thus the
number of bands. At 600 DPI this is normally 4Mbyte, so a reasonable
approximate at 200 DPI is 450k. Thus BufferSpace is also set.

* [ghostscript] Enable another sanitizer to see more issues.
 		2020-04-07 09:10:11 -07:00
docs [CIFuzz] Documentation update (#3572) 2020-04-02 12:36:17 -07:00
infra [infra] Add build retry logic inside wait_for_build.py (#419). (#3585) 2020-04-06 18:58:09 -07:00
projects Update flags and enable new sanitizer (#3587) 2020-04-07 09:10:11 -07:00
.gitignore [infra] replacing wget with ADD where possible 2016-12-28 14:09:09 -08:00
.pylintrc Merge contradictory indent directives (#3226) 2020-01-13 09:34:28 -08:00
.style.yapf [infra] Add presubmit script (#3196) 2020-01-10 10:19:42 -08:00
.travis.yml [infra] Presubmit fix - test (#3443) 2020-03-05 08:44:18 -08:00
CONTRIBUTING.md Fix hyperlink markdown (#2926) 2019-10-08 10:48:41 -07:00
LICENSE Create LICENSE 2016-10-03 12:24:25 -07:00
README.md Upgrade lcamtuf.coredump.cx to HTTPS, as it has been (#3527) 2020-03-20 07:50:16 -07:00
oss-fuzz.iml Add jekyll generator for docs. (#2660) 2019-08-06 13:29:19 -07: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, 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 and AFL 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, and Go 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 2020, OSS-Fuzz has found over 16,000 bugs in 250 open source projects.

Blog posts