clusterfuzz icon indicating copy to clipboard operation
clusterfuzz copied to clipboard

Scalable fuzzing infrastructure.

Results 425 clusterfuzz issues
Sort by recently updated
recently updated
newest added

Similar to #860. There are some crashes reported in https://oss-fuzz.com/testcases?project=wasmtime and it seems that certain stackframes could be skipped (e.g. `abort`, `abort_internal`, `rust_panic_with_hook`, etc). Not sure who assign this to....

core feature

this was discussed in https://github.com/google/clusterfuzz/pull/1333 https://reviews.llvm.org/D73136 was landed a month ago as https://github.com/llvm/llvm-project/commit/15f1d5d14425528540e1cc4aa776b195a2e1e7e0 and we're using https://github.com/llvm/llvm-project/commit/c29003813ab9bd6ea7b6de40ea8f1fe21979f13f which is a newer revision which means now we can check the presence...

Continuation of https://github.com/google/clusterfuzz/issues/503. The corresponding issue on OSS-Fuzz side is https://github.com/google/oss-fuzz/issues/1632

core feature

As is, running Python 2 black box fuzzers does not work from the Python 3 bot, as we invoke "python run.py ..." where `python` is Python 3. We need to...

Py2->3

Blocked on #183. We can re-enable this once the migration is complete. Initially disabled in #1226.

core feature

Sanitizer options should be minimized in a similar fashion to command line arguments during minimization. We currently specify a long list of sanitizer options, and most of them aren't needed....

core feature

This is similar to variant task breakage (see https://github.com/google/clusterfuzz/pull/1083). This happens since we try to minimize AFL testcases with libFuzzer and code gets confused whether to use new engine impl...

core feature

Hi, I'm opening this issue because documentation about local instance is not complete imo, I was able to run a local instance with: `python butler.py run_server` And then a bot...

documentation

And also possibly move some of our hacks into upstream AFL now that we own the repo.

core feature

This was requested in https://bugs.chromium.org/p/chromium/issues/detail?id=997940, //cc @pwnall I think we're currently using a constant timeout for minimization. Should we consider increasing it for large testcases and maybe decreasing for smaller...

bug