commit | ce9a7623e943811a44becd067f624949d7c8a921 | [log] [tgz] |
---|---|---|
author | Nicolás Peña Moreno <npm@chromium.org> | Fri Oct 18 15:05:49 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Oct 18 15:05:49 2019 |
tree | edb2ab16c81fbda9cf18ddb8eae986acc001db34 | |
parent | bb77cbb79f1720ff73ee8e9fa3ccc7323849ddfb [diff] |
Add a fuzzer for DateTimeFormat::Parse Change-Id: I9f45508bb229a809e15423c5d9f48271702719af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866558 Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Reviewed-by: Jeremy Roman <jbroman@chromium.org> Reviewed-by: Max Moroz <mmoroz@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#707372} Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src Cr-Mirrored-Commit: 1ec4f4817913203fb0ba39cd30e664ee0c3bea45
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.