Searched +full:fuzz +full:- +full:bugs (Results 1 – 25 of 222) sorted by relevance
123456789
| /external/cronet/testing/libfuzzer/ |
| D | README.md | 1 # Fuzz testing in Chromium
3 [go/chrome-fuzzing](https://goto.google.com/chrome-fuzzing)
5 [Fuzzing] is a testing technique that feeds auto-generated inputs to a piece
8 [go/fuzzing-success](http://go/fuzzing-success)). You can learn more about the
9 benefits of fuzzing at [go/why-fuzz](http://go/why-fuzz).
11 This documentation covers the in-process guided fuzzing approach employed by
13 out-of-process fuzzers, please refer to the [Blackbox fuzzing] page in the
20 In Chromium, you can easily create and submit fuzz targets. The targets are
24 You should fuzz any code which absorbs inputs from untrusted sources, such
26 it's an especially good idea to fuzz it.
[all …]
|
| D | AFL_integration.md | 4 set of fuzz targets as libfuzzer. This support has now been disabled.
8 * [AFL Chromium bugs] - bugs found by AFL in Chromium.
9 * [AFL OSS-Fuzz bugs] - bugs found by AFL in [OSS-Fuzz].
12 [AFL Chromium bugs]: https://bugs.chromium.org/p/chromium/issues/list?can=1&q=afl_chrome_asan+-stat…
13 [AFL OSS-Fuzz bugs]: https://bugs.chromium.org/p/oss-fuzz/issues/list?can=1&q=label%3AEngine-afl%2C…
|
| D | reference.md | 9 Thus, our [reproduce tool] cannot reproduce bugs found using MSan.
11 run MSan-instrumented code in docker.
33 |---------|-------------|
34 |Linux ASan | `tools/mb/mb.py gen -m chromium.fuzz -b 'Libfuzzer Upload Linux ASan' out/libfuzzer` |
35 |Linux ASan (x86) | `tools/mb/mb.py gen -m chromium.fuzz -b 'Libfuzzer Upload Linux32 ASan' out/lib…
36 |Linux ASan Debug | `tools/mb/mb.py gen -m chromium.fuzz -b 'Libfuzzer Upload Linux ASan Debug' out…
37 |Linux MSan[*](#MSan) | `tools/mb/mb.py gen -m chromium.fuzz -b 'Libfuzzer Upload Linux MSan' out/l…
38 |Linux UBSan[*](#UBSan)| `tools/mb/mb.py gen -m chromium.fuzz -b 'Libfuzzer Upload Linux UBSan' out…
39 |Chrome OS ASan | `tools/mb/mb.py gen -m chromium.fuzz -b 'Libfuzzer Upload Chrome OS ASan' out/lib…
40 |Mac ASan | `tools/mb/mb.py gen -m chromium.fuzz -b 'Libfuzzer Upload Mac ASan' out/libfuzzer` |
[all …]
|
| /external/oss-fuzz/docs/ |
| D | faq.md | 1 ---
7 ---
11 - TOC
13 ---
19 [useful links]({{ site.baseurl }}/reference/useful-links/#tutorials) page.
27 user security. We will consider each request on a case-by-case basis, but some
30 - Exposure to remote attacks (e.g. libraries that are used to process
32 - Number of users/other projects depending on this project.
37 ## How can I find potential fuzz targets in my open source project?
41 - consume un-trusted data from users or from the network.
[all …]
|
| D | index.md | 1 ---
3 title: OSS-Fuzz
8 ---
10 # OSS-Fuzz
12 [Fuzz testing] is a well-known technique for uncovering programming errors in
15 vulnerabilities and stability bugs by deploying [guided in-process fuzzing of
19 [Fuzz testing]: https://en.wikipedia.org/wiki/Fuzz_testing
21 [thousands]: https://bugs.chromium.org/p/chromium/issues/list?q=label%3AStability-LibFuzzer%2CStabi…
22 [guided in-process fuzzing of Chrome components]: https://security.googleblog.com/2016/08/guided-in…
25 OSS-Fuzz aims to make common open source software more secure and stable by
[all …]
|
| /external/oss-fuzz/docs/advanced-topics/ |
| D | bug_fixing_guidance.md | 1 ---
5 permalink: /advanced-topics/bug-fixing-guidance
6 ---
11 This page provides brief guidance on how to prioritise and fix bugs reported by
12 OSS-Fuzz.
14 - TOC
18 In general the severity of an issue reported by OSS-Fuzz must be determined
20 the fuzzers OSS-Fuzz makes an effort into determining the severity of the bug
27 the OSS-Fuzz testcase page and you can also search up all of these on monorail
28 using the search pattern `-Bug=security`.
[all …]
|
| D | reproducing.md | 1 ---
6 permalink: /advanced-topics/reproducing/
7 ---
9 # Reproducing OSS-Fuzz issues
12 You've been CCed on an OSS-Fuzz issue
13 ([examples](https://bugs.chromium.org/p/oss-fuzz/issues/list?can=1&q=Type%3ABug%2CBug-Security)).
17 - TOC
19 ---
21 ## Fuzz target bugs
25 Download it. This file contains the bytes that were fed to the [fuzz
[all …]
|
| D | ideal_integration.md | 1 ---
6 permalink: /advanced-topics/ideal-integration/
7 ---
9 # Ideal integration with OSS-Fuzz
13 implement and maintain fuzz targets or integrate them with OSS-Fuzz in the same
19 [example](https://github.com/google/oss-fuzz/tree/master/projects/example/my-api-repo)
22 - TOC
24 ---
28 Every [fuzz target](http://libfuzzer.info/#fuzz-target):
29 * Is [maintained by code owners](#fuzz-target) in their RCS (Git, SVN, etc).
[all …]
|
| /external/jazzer-api/docs/ |
| D | findings.md | 3 Jazzer has found the following vulnerabilities and bugs.
5 …r is used to fuzz JVM projects in OSS-Fuzz, further findings are listed [on the OSS-Fuzz issue tra…
7 If you find bugs with Jazzer, we would like to hear from you!
12 …--------------------------------------------------------------------------------------------------…
13 …62a941) | [CVE-2022-41853](https://nvd.nist.gov/vuln/detail/CVE-2022-41853) | [OSS-F…
14 …-h4h5-3hr4-j3g2) | [CV…
15 …-01-18) …
16 …-01-18) …
17 …-wrvw-hg22-4m67) | [CV…
18 …Bugs found in HTML and XML parser | [fixed](https:/…
[all …]
|
| /external/tensorflow/tensorflow/security/fuzzing/ |
| D | tf_fuzzing.bzl | 1 """Definitions for rules to fuzz TensorFlow."""
5 # For a fuzzer ${FUZZ} we have the following setup:
6 # - ${FUZZ}_fuzz.cc : the implementation of the fuzzer
7 # - corpus/${FUZZ}/... : public corpus for the fuzzer
8 # - dictionaries/${FUZZ}.dict : fuzzing dictionary for the fuzzer
9 # - ${FUZZ}_internal/... : internal data for the fuzzer
11 # If a fuzzer needs some framework to build, we can use the ${FUZZ}_internal/
18 # The internal folder can also contain proto definitions (if using proto-based
29 # Reporting bugs arguments, not used in open source
38 """Specify how to build a TensorFlow fuzz target.
[all …]
|
| /external/oss-fuzz/docs/oss-fuzz/ |
| D | architecture.md | 1 ---
6 parent: OSS-Fuzz
7 ---
10 
15 one or more [fuzz targets](http://libfuzzer.info/#fuzz-target)
16 and [integrates]({{ site.baseurl }}/advanced-topics/ideal-integration/) them
18 1. The project is [accepted to OSS-Fuzz]({{ site.baseurl }}/getting-started/accepting-new-projects/…
19 1. The OSS-Fuzz [builder](https://github.com/google/oss-fuzz/tree/master/infra/build) builds the pr…
20 1. The builder uploads the fuzz targets to the OSS-Fuzz GCS bucket.
21 1. [ClusterFuzz]({{ site.baseurl }}/further-reading/clusterfuzz) downloads the fuzz targets and beg…
[all …]
|
| /external/oss-fuzz/ |
| D | README.md | 1 # OSS-Fuzz: Continuous Fuzzing for Open Source Software
3 [Fuzz testing] is a well-known technique for uncovering programming errors in
6 vulnerabilities and stability bugs by deploying [guided in-process fuzzing of
10 [Fuzz testing]: https://en.wikipedia.org/wiki/Fuzz_testing
12 [thousands]: https://bugs.chromium.org/p/chromium/issues/list?q=label%3AStability-LibFuzzer%2CStabi…
13 [guided in-process fuzzing of Chrome components]: https://security.googleblog.com/2016/08/guided-in…
16 OSS-Fuzz aims to make common open source software more secure and stable by
32 Currently, OSS-Fuzz supports C/C++, Rust, Go, Python and Java/JVM code. Other languages
33 supported by [LLVM] may work too. OSS-Fuzz supports fuzzing x86_64 and i386
39 
[all …]
|
| /external/pigweed/pw_fuzzer/guides/ |
| D | reproducing_oss_fuzz_bugs.rst | 1 .. _module-pw_fuzzer-guides-reproducing_oss_fuzz_bugs:
4 pw_fuzzer: Using OSS-Fuzz
6 .. pigweed-module-subpage::
9 .. TODO: b/281139237 - Update with better instructions for downstream projects.
11 Core Pigweed is integrated with `OSS-Fuzz`_, a continuous fuzzing infrastructure
16 -------------------------
17 Reproducing Bugs Directly
18 -------------------------
20 Bugs produced by OSS-Fuzz can be found in its `Monorail instance`_. These bugs
31 :ref:`module-pw_fuzzer-guides`.
[all …]
|
| /external/oss-fuzz/infra/triage-party/ |
| D | oss-fuzz.yaml | 2 name: oss-fuzz
4 - https://github.com/google/oss-fuzz
7 - id: Fuzzing Issues
11 Status of issues across oss-fuzz repos
14 - fuzz-issue-updated-support
16 - fuzz-bugs
17 - fuzz-priority
19 - fuzz-many-reactions
20 - fuzz-many-commenters
21 - fuzz-issue-zombies
[all …]
|
| /external/freetype/docs/oldlogs/ |
| D | ChangeLog.28 | 1 2017-09-16 Werner Lemberg <wl@gnu.org>
7 Tag sources with `VER-2-8-1'.
24 builds/wince/vc2005-ce/freetype.vcproj,
25 builds/wince/vc2005-ce/index.html,
26 builds/wince/vc2008-ce/freetype.vcproj,
27 builds/wince/vc2008-ce/index.html: s/2.8/2.8.1/, s/28/281/.
34 2017-09-13 suzuki toshiya <mpsuzuki@hiroshima-u.ac.jp>
38 __builtin_shuffle() was introduced in gcc-4.7. The lowest
41 * src/sfnt/pngshim.c (premultiply_data): Fix cpp-macro to
45 2017-09-13 suzuki toshiya <mpsuzuki@hiroshima-u.ac.jp>
[all …]
|
| /external/skia/fuzz/ |
| D | README.md | 8 These fuzzers are packaged in two different ways (see //BUILD.gn). There is a `fuzz` executable
9 that contains all fuzzers and is a convenient way to reproduce fuzzer-reported bugs. There are also
13 See [../site/dev/testing/fuzz.md] for more information on building and running fuzzers using the
14 `fuzz` executable.
17 We fuzz Skia using [OSS-Fuzz](https://github.com/google/oss-fuzz), which in turn uses fuzzing
18 engines such as libfuzzer, afl-fuzz, hong-fuzz, and others to fuzz Skia. OSS-Fuzz will automatically
19 [file and close bugs](https://bugs.chromium.org/p/oss-fuzz/issues/list?q=label:Proj-skia) when
22 There is a [Skia folder](https://github.com/google/oss-fuzz/tree/master/projects/skia)
23 in the OSS-Fuzz repo that we make changes to when we want to add/remove/change the fuzzers that
25 [This](https://google.github.io/oss-fuzz/getting-started/new-project-guide/#testing-locally)
[all …]
|
| /external/oss-fuzz/docs/getting-started/ |
| D | new_project_guide.md | 1 ---
7 permalink: /getting-started/new-project-guide/
8 ---
13 - TOC
15 ---
21 - [Integrate]({{ site.baseurl }}/advanced-topics/ideal-integration/) one or more [fuzz targets]({{ …
22 with the project you want to fuzz.
25 [boringssl](https://github.com/google/boringssl/tree/master/fuzz) or
27 [go-fuzz](https://github.com/dvyukov/go-fuzz-corpus/tree/86a5af9d6842f80b205a082538ea28f61bbb8ccb) …
31 - [Install Docker](https://docs.docker.com/engine/installation)
[all …]
|
| /external/libprotobuf-mutator/ |
| D | README.md | 1 # libprotobuf-mutator
3 …Build Status](https://travis-ci.org/google/libprotobuf-mutator.svg?branch=master)](https://travis-…
4 …oss-fuzz-build-logs.storage.googleapis.com/badges/libprotobuf-mutator.svg)](https://oss-fuzz-build…
7 libprotobuf-mutator is a library to randomly mutate
16 sudo apt-get update
17 sudo apt-get install protobuf-compiler libprotobuf-dev binutils cmake \
18 ninja-build liblzma-dev libz-dev pkg-config autoconf libtool
26 cmake .. -GNinja -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_BUILD_TYPE=Debug
31 By default, the system-installed version of
44 This installs the headers, pkg-config, and static library.
[all …]
|
| /external/skia/site/docs/dev/gardening/ |
| D | gpu.md | 2 ---
6 ---
20 ----------------------------
24 …-related bugs from clients in various bug trackers. This means triaging and assigning bugs that ha…
33 …bugs. The balance of a gardener's time should be spent divided as seen fit between 2) and 3). It i…
35 …'s job is NOT to spend an abnormal amount of time triaging images, filing bugs for failing bots, o…
39 --------------------------
47 -----------------------------------
55 ---------------------------
62 ----------------------
[all …]
|
| D | _index.md | 1 ---
6 ---
10 - [What does a Skia Gardener do?](#what_is_a_skia_gardener)
11 - [Skia tree](#skia_tree)
12 - [Triage](#triage)
13 - [Blamer](#blamer)
14 - [AutoRollers](#autorollers)
15 - [Gold and Perf](#gold_and_perf)
16 - [Documentation](#skia_gardener_doc)
17 - [Preparing for your rotation](#preparations)
[all …]
|
| /external/oss-fuzz/docs/further-reading/ |
| D | clusterfuzz.md | 1 ---
6 permalink: /further-reading/clusterfuzz/
7 ---
12 infrastructure behind OSS-Fuzz. It was initially built for fuzzing Chrome at
15 - TOC
17 ---
21 ClusterFuzz provides a [web interface](https://oss-fuzz.com)
22 to view statistics about your fuzz targets, as well as current crashes.
29 ClusterFuzz will automatically de-duplicate and file reproducible crashes into
30 our [bug tracker](https://bugs.chromium.org/p/oss-fuzz/issues/list). We provide
[all …]
|
| /external/pigweed/pw_fuzzer/ |
| D | docs.rst | 1 .. _module-pw_fuzzer:
6 .. pigweed-module::
9 Use state of the art tools to automatically find bugs in your C++ code with 5
13 .. code-block:: cpp
18 ----------
20 ----------
22 tests pass. But could there be bugs in inputs or code paths the unit tests do
25 However, fuzzing requires some complex interactions between compiler-added
30 See :ref:`module-pw_fuzzer-concepts` to learn more about the different
31 components of a fuzzer and how they work together to discover hard-to-find bugs.
[all …]
|
| /external/oss-fuzz/docs/clusterfuzzlite/ |
| D | running_clusterfuzzlite.md | 1 ---
7 permalink: /clusterfuzzlite/running-clusterfuzzlite/
8 ---
12 - TOC
14 ---
38 This use-case is important because it allows ClusterFuzzLite to find bugs before
40 To use Code Review Fuzzing, set the configuration option `clusterfuzzlite-task`
41 to `code-review`.
42 If you are familiar with OSS-Fuzz's CIFuzz, this task is similar to CIFuzz.
47 introduced bugs and use the corpus developed during batch fuzzing.
[all …]
|
| /external/oss-fuzz/infra/cifuzz/ |
| D | run_fuzzers.py | 7 # http://www.apache.org/licenses/LICENSE-2.0
28 # pylint: disable=wrong-import-position,import-error
55 """Returns fuzz targets in out directory."""
87 logging.info('Fuzz targets: %s', self.fuzz_target_paths)
89 logging.error('No fuzz targets were found in out directory: %s.',
95 def cleanup_after_fuzz_target_run(self, fuzz_target_obj): # pylint: disable=no-self-use
99 def run_fuzz_target(self, fuzz_target_obj): # pylint: disable=no-self-use
112 artifact_name = (f'{target.target_name}-{self.config.sanitizer}-'
117 """Returns a fuzz target object."""
122 """Runs fuzz targets. Returns True if a bug was found."""
[all …]
|
| /external/AFLplusplus/utils/ |
| D | README.md | 5 - aflpp_driver - easily instrument LLVMFuzzerTestOneInput()
8 - afl_network_proxy - fuzz a target over the network: afl-fuzz on
11 - plot_ui - simple UI window utility to display the
12 plots generated by afl-plot
14 - afl_proxy - skeleton file example to show how to fuzz
18 - afl_untracer - fuzz binary-only libraries much faster but with
21 - analysis_scripts - random -o out analysis scripts
23 - argv_fuzzing - a simple wrapper to allow cmdline to be fuzzed
26 - asan_cgroups - a contributed script to simplify fuzzing ASAN
29 - autodict_ql - generate dictionary files from source code.
[all …]
|
123456789