aml_sdk_331310010 (9319133,com.google.android.sdkext)
Snap for 8603585 from 964a594e4219fae93e07d1546c905a01e3bf8e3e to mainline-sdkext-release

Change-Id: I68c3be2d3c61861bc640c80c7147d50ae2efa11e
tree: aab00ff7a7202a49d2afaa9084f260c2e519653b
  1. .github/
  2. docs/
  3. infra/
  4. projects/
  5. .dockerignore
  6. .gitignore
  7. .pylintrc
  8. .style.yapf
  9. Android.bp
  10. CONTRIBUTING.md
  11. LICENSE
  12. METADATA
  13. MODULE_LICENSE_APACHE2
  14. OWNERS
  15. README.md
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, Python and Java/JVM 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 June 2021, OSS-Fuzz has found over 30,000 bugs in 500 open source projects.

Blog posts