This is the mail archive of the
mailing list for the binutils project.
Re: [oss-security] Re: Fuzzing objdump (PR 17512) and readelf (PR 17531)
- From: Yury Gribov <y dot gribov at samsung dot com>
- To: oss-security at lists dot openwall dot com
- Cc: binutils at sourceware dot org, cherepan at mccme dot ru
- Date: Fri, 07 Nov 2014 14:43:39 +0300
- Subject: Re: [oss-security] Re: Fuzzing objdump (PR 17512) and readelf (PR 17531)
- Authentication-results: sourceware.org; auth=none
- References: <545C4DEF dot 5030600 at mccme dot ru> <545C9A09 dot 7030007 at samsung dot com> <20141107115906 dot 7140b89d at pc>
On 11/07/2014 01:59 PM, Hanno Böck wrote:
Am Fri, 07 Nov 2014 13:08:09 +0300
schrieb Yury Gribov <email@example.com>:
This looks rather impressive. Have you considered automatically
detecting duplicates by e.g. analyzing stacktraces?
american-fuzzy-lop kind of does that. It creates a hash among the code
path and groups fuzzing samples by that. That's quite convenient.
[Cc-ing Binutils ML back again]
Yeah, I think there was even an article in one of recent PLDIs which
discussed different approaches to filtering duplicates arising in
compiler fuzz testing (they did various combinations of stacktraces,
Valgrind output, program coverage, etc.). I was just curious how well
this works for real world tasks like objdump crashes.