| commit | d144db463f6842c21d13cd3123ae6caabe1da448 | [log] [tgz] |
|---|---|---|
| author | Clemens Backes <clemensb@chromium.org> | Wed Jun 08 03:43:14 2022 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jun 08 03:53:33 2022 |
| tree | 12a6e1caeca9942b5ac6ec40a7efe04b8828ef80 | |
| parent | 5e9ff5786d09585a1c0dea3db9fb3e459bb0a9ac [diff] |
Add v8_wasm_streaming_fuzzer The fuzzer was added to V8 in https://crrev.com/c/3675100. R=inferno@chromium.org Bug: v8:12922 Change-Id: Ic7253f3eba56b82674af5c51f9b4f3529a344ab4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3673527 Auto-Submit: Clemens Backes <clemensb@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Oliver Chang <ochang@chromium.org> Reviewed-by: Oliver Chang <ochang@chromium.org> Cr-Commit-Position: refs/heads/main@{#1011810} NOKEYCHECK=True GitOrigin-RevId: 6ab8dac9f72e3119c2a8d4f3c6ebbe4b218b4994
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.