commit | 628d39bb19a4b503828587a0c406cad9c3aea951 | [log] [tgz] |
---|---|---|
author | android-build-team Robot <android-build-team-robot@google.com> | Tue Nov 05 12:48:21 2019 +0000 |
committer | android-build-team Robot <android-build-team-robot@google.com> | Tue Nov 05 12:48:21 2019 +0000 |
tree | b7da7abb06b3fdc15d6bb074d5194d103bf016f4 | |
parent | 4d145c66e9a8eb00fdacb57609f84038a78bda0d [diff] | |
parent | 2d80de24b8dd06ab4fa506f5aa5a93cebb35b67a [diff] |
Snap for 5988121 from 2d80de24b8dd06ab4fa506f5aa5a93cebb35b67a to qt-aml-networking-release Change-Id: I91365efcb78102d71c174003515f4f2d138e45a7
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.
Read our detailed documentation to learn how to use OSS-Fuzz.
As of August 2019, OSS-Fuzz has found over 14,000 bugs in 200 open source projects.