commit | 446d0398a0edbaaf8d831a582ca1c2c2f1ff3199 | [log] [tgz] |
---|---|---|
author | Glen Robertson <glenrob@chromium.org> | Fri Mar 19 03:05:27 2021 |
committer | Copybara-Service <copybara-worker@google.com> | Fri Mar 19 03:11:58 2021 |
tree | 1055a7248ca383fc99376f588f6bedbe4d870c73 | |
parent | e6ef327fceb2bef23bba55aaa5914b79db3559e1 [diff] |
Fix broken link Change-Id: Icb97c58bf78b36539b12fb1fa2c732d68937cfc8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2775118 Reviewed-by: Glen Robertson <glenrob@chromium.org> Reviewed-by: Abhishek Arya <inferno@chromium.org> Auto-Submit: Glen Robertson <glenrob@chromium.org> Commit-Queue: Abhishek Arya <inferno@chromium.org> Cr-Commit-Position: refs/heads/master@{#864544} GitOrigin-RevId: 57bd25bf5ba1dc33e15fce4463420a96578d599d
Fuzzing is a testing technique that feeds auto-generated inputs to a piece of target code in an attempt to crash the code. It's one of the most effective methods we have for finding security and stability issues (see go/fuzzing-success). You can learn more about the benefits of fuzzing at go/why-fuzz.
This documentation covers the in-process guided fuzzing approach employed by different fuzzing engines, such as libFuzzer or AFL. To learn more about out-of-process fuzzers, please refer to the Blackbox fuzzing page in the ClusterFuzz documentation.
In Chromium, you can easily create and submit fuzz targets. The targets are automatically discovered by buildbots, built with different fuzzing engines, then uploaded to the distributed ClusterFuzz fuzzing system to run at scale.
Create your first fuzz target and submit it by stepping through our Getting Started Guide.
Creating a fuzz target that expects a protobuf instead of a byte stream as input.
Reproducing bugs found by libFuzzer/AFL and reported by ClusterFuzz.
Fuzzing mojo interfaces using automatically generated libprotobuf-mutator fuzzers.