commit | 8f2f5be81156444ff1a55bb34f12db770f2c6eb1 | [log] [tgz] |
---|---|---|
author | Android Build Role Account android-build-prod <android-build-team-robot@google.com> | Sat Feb 15 01:00:36 2020 +0000 |
committer | Android Build Role Account android-build-prod <android-build-team-robot@google.com> | Sat Feb 15 01:00:36 2020 +0000 |
tree | 06d9c76fcd1e50965e3f13ae2830af0aa8fdbf79 | |
parent | 579635d4f6339dda3bec1405a5ecb5a55eb4eb47 [diff] | |
parent | 5e473359caa4f374621ea8ce48dc84a91e4d3fc9 [diff] |
Snap for 6209820 from 5e473359caa4f374621ea8ce48dc84a91e4d3fc9 to r-keystone-qcom-release Change-Id: I4bd102504953a16d99367f8873de24b07e87ce90
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 January 2020, OSS-Fuzz has found over 16,000 bugs in 250 open source projects.