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.
9,398 Commits 195 Branches 0 Tags 124 MiB
Shell 27.3%
Python 19.2%
Dockerfile 17.4%
Java 17%
C 7.2%
Other 11.7%
Go to file
Arthur Chan 5b7f4f0317
zip4j: Add retry handler setting for maven build (#10429) 
The Maven build process requires fetching dependency libraries from the
central repository with Apache Wagon. This fetching action will fail
because of an unstable connection or connection rest by the repository
server because there are too many fetching requests. By default, maven
build does not retry the fetching if it is not an error in the
request-sending methods. Thus these failing dependency fetching will
cause maven project fail to build randomly. This PR fixes the build
script to configure the maven wagon parameter to force it to retry when
failing and also increases the timeout and retry count to decrease the
chance of build failure from dependencies fetching failure cases.

Signed-off-by: Arthur Chan <arthur.chan@adalogics.com>
 		2023-05-31 15:56:45 +01:00
.allstar Opt out of allstar binary artifacts check (#7816) 2022-06-08 09:37:08 -04:00
.clusterfuzzlite Fuzz OSS-Fuzz with Atheris and ClusterFuzzLite (#8985) 2022-11-30 15:37:36 -05:00
.github Remove none build from CI. (#10189) 2023-04-30 21:40:06 -04:00
docs docs: add a list with available sanitizers (#10387) 2023-05-25 12:43:19 -04:00
infra [CIfuzz] Fix SARIF functionality. (#10349) 2023-05-31 09:33:58 -04:00
projects zip4j: Add retry handler setting for maven build (#10429) 2023-05-31 15:56:45 +01: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 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 Add missing blog posts (#9569) 2023-02-03 01:51:08 +00: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 February 2023, OSS-Fuzz has helped identify and fix over 8,900 vulnerabilities and 28,000 bugs across 850 projects.

Blog posts