commit | 8b63fe958bc5aea0a2721e9746f6e12e9453fffe | [log] [tgz] |
---|---|---|
author | Haibo Huang <hhb@google.com> | Tue Sep 24 16:40:01 2019 -0700 |
committer | Haibo Huang <hhb@google.com> | Tue Sep 24 16:40:01 2019 -0700 |
tree | b7da7abb06b3fdc15d6bb074d5194d103bf016f4 | |
parent | 4a6b9207ec21221dc351b287d087a082dc55f277 [diff] | |
parent | 97060c44dec9c25b8c74a4ee05a217bd68f119fe [diff] |
Upgrade oss-fuzz to 97060c44dec9c25b8c74a4ee05a217bd68f119fe Test: None Change-Id: Ice113437769207d0db1493d9bb105baac207f6a6
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.