A fuzzy issue of responsible disclosure
A fuzzy issue of responsible disclosure
Posted Aug 13, 2022 18:18 UTC (Sat) by sfeam (subscriber, #2841)In reply to: A fuzzy issue of responsible disclosure by developer122
Parent article: A fuzzy issue of responsible disclosure
My experience as a developer receiving a slew of fuzz-generated "crash-causing input" reports is that a huge fraction of the submitted cases tend to hit the same small number of actual bugs in the code. Even if 100% of the submitted bad inputs yield reproducible crashes of the unpatched code, finding and fixing the cause of a single representative submission may clear anywhere up to all of the remaining submission from the reproducible category when run on the now-patched code.
So a larger number of fuzz-generated bug reports does not necessarily translate to a proportionally larger amount of work. I think it is unreasonable to expect a reporter to identify in advance how much redundancy is in their set of fuzz bugs. That would amount to a stricture "only report bugs for which you have already found a fix".
