commit | e4ac2ea97cb55bdcfc9d843a7b5c41ee35dc20cc | [log] [tgz] |
---|---|---|
author | Haibo Huang <hhb@google.com> | Wed May 13 21:51:05 2020 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed May 13 21:51:05 2020 +0000 |
tree | 2c7efc415ea4df9f7d70c9e555287a7caff537ef | |
parent | 4e1dbe97a9038963a81f9f32669d216028fa533d [diff] | |
parent | cbda9eb12254e5fadfcd7dbb25a7a5807c380ba3 [diff] |
Upgrade oss-fuzz to 982ddca0351851891e55093717dbe8b76404b382 am: cbda9eb122 Change-Id: I957241e5feab39ddbc45a1d3358fbaf53ac60486
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.