Upgrade oss-fuzz to 167aec47bf047e3b3ccf01c5e4e3030144e86eea

Test: make
Change-Id: I30c71503664ec913c7ce67de13aa1297cb3837db
tree: e8b34a746985a5fda651788765d3d0e30f1e7e8a
  1. .dockerignore
  2. .github/
  3. .gitignore
  4. .pylintrc
  5. .style.yapf
  6. Android.bp
  7. CONTRIBUTING.md
  8. LICENSE
  9. METADATA
  10. MODULE_LICENSE_APACHE2
  11. OWNERS
  12. README.md
  13. docs/
  14. infra/
  15. oss-fuzz.iml
  16. projects/
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