FuzzBench Feedback and Improvements

JavaScript isn't enabled in your browser, so this file can't be opened. Enable and reload.

Thank you for taking 5-10 minutes to complete this survey.

Your feedback will help us better understand researchers' needs and prioritize enhancements for FuzzBench. Your insights are invaluable in shaping the future development of the platform and benefiting the vulnerability discovery community.

Email *

Have you had a chance to use FuzzBench? *

Yes, I have used it recently.

Yes, I have used it years ago.

No, I have not. (Please answer the following questions based on your general expectation of a fuzzing evaluation platform.)

Is there anything that makes it difficult or impossible for you to use FuzzBench?

How would you rate FuzzBench based on your experience or our documentation? (1 = Poor, 5 = Excellent)

Clear selection

What features do you find most valuable in a fuzzing evaluation platforms (e.g., FuzzBench or others you used)? (Select all that apply)
*

Comprehensive benchmark suite

Easy to integrate my fuzzer to the platform

Reproducible results

Rigorous and reliable evaluation process

Offers well-established fuzzers as a foundation for custom improvements

Provides fuzzers used in industry as evaluation baselines

Fast and free evaluation

Other:

Required

How would you rate the importance of following properties to a general fuzzing evaluation platform (FuzzBench or others)?

(1 = least important, 5 = most important, tick 'None' on empty rows)

More coverage-based benchmarks

More bug-based benchmarks

More fuzzers as customization foundation or evaluation baselines.

Easier fuzzer integration

More detailed documentation

None

Please elaborate more on your decision on the previous question.

(e.g., How many benchmarks? What part makes fuzzer integration difficult?)

Would including the following statistics in a fuzzing evaluation report be useful to you?

(1 = least important, 5 = most important, tick 'None' on empty rows)

Unique coverage (lines only covered by each fuzzer)

Lines missed by each fuzzer

Conditions that block fuzzing

Memory consumption of each fuzzer

Time taken by each fuzzer to find a bug

Area under curve of each fuzzer in the coverage/bug vs. time plot

Benchmark properties (program size, seed size, equality comparison proportion, etc.)

Is there any specific statistics that you would like to measure in a fuzzing evaluation report?

Would evaluating automate fuzz targets generation be useful to you? For example, given a library under test and a fuzzer, we evaluate if the fuzz target automatically generated by your program that can allow the fuzzer to test more APIs of the library. *

Yes, I am working on this topic

Yes, but it can be useful to my future research works

No, it is not promising

Other:

What other improvements, comments, or feedback to share with the FuzzBench team?

Send me a copy of my responses.

Submit

Clear form

Never submit passwords through Google Forms.

reCAPTCHA

Privacy Terms

This form was created inside of Google.com. Privacy & Terms

Forms