[HN Gopher] Autofz: Automated Fuzzer Composition at Runtime
       ___________________________________________________________________
        
       Autofz: Automated Fuzzer Composition at Runtime
        
       Author : PaulHoule
       Score  : 36 points
       Date   : 2023-03-01 00:59 UTC (1 days ago)
        
 (HTM) web link (arxiv.org)
 (TXT) w3m dump (arxiv.org)
        
       | albntomat0 wrote:
       | What's with fuzzing papers comparing against older fuzzers, and
       | not AFL++?
       | 
       | In this particular case, they specifically mention using
       | particular parts of AFL++, but not the whole thing.
       | 
       | To me, this is a consistent "smell" about the quality of the
       | fuzzer & paper.
        
       | tsgates wrote:
       | Thanks for sharing the work.
       | 
       | Tl;dr. autofz is a meta fuzzer that combines a group of fuzzers
       | and outperforms each of individual fuzzers. Since each fuzzer
       | shows completely different characteristics for each targets, it
       | was cumbersome for developers to determine which fuzzer to adopt
       | and to evaluate them for best fit. With autofz, it simply figures
       | out -- based on past execution behavior and responses of each
       | fuzzer, at runtime, and allocates the proper resource to maximize
       | the output (i.e., bug finding and code coverage) of the fuzzing
       | process.
        
       | aarchi wrote:
       | The (preprint) paper links to its repository, where its code
       | eventually will be. I suspect it will be pushed around August
       | 2023, before USENIX Security'23, where it will be published.
       | 
       | https://github.com/sslab-gatech/autofz
        
       ___________________________________________________________________
       (page generated 2023-03-02 23:02 UTC)