{"id":2918,"date":"2010-07-28T10:52:54","date_gmt":"2010-07-28T09:52:54","guid":{"rendered":"https:\/\/www.darknet.org.uk\/?p=2918"},"modified":"2015-09-09T19:37:27","modified_gmt":"2015-09-09T11:37:27","slug":"fuzzdiff-tool-for-fuzzing-and-crash-analysis","status":"publish","type":"post","link":"https:\/\/www.darknet.org.uk\/2010\/07\/fuzzdiff-tool-for-fuzzing-and-crash-analysis\/","title":{"rendered":"FuzzDiff – Tool For Fuzzing and Crash Analysis"},"content":{"rendered":"
[ad]<\/p>\n
FuzzDiff is a simple tool to help make crash analysis during file format fuzzing a bit easier. I’m sure many people have written similar tools for their own purposes, but I haven’t seen any that are publicly available. Hopefully at least one person finds it useful.<\/p>\n
When provided with a fuzzed file, a corresponding original un-fuzzed file, and the path to the targeted program, FuzzDiff will selectively “un-fuzz” portions of the fuzzed file while re-launching the application to monitor for crashes. This will yield a file that still crashes the target application, but contains a minimum set of changes from the original, un-fuzzed file. This can be useful in pinning down the exact cause of a crash.<\/p>\n
The tool is written in Python and currently only works on Unix-based systems, since it monitors for crashes by checking for SIGSEGV. It also assumes that the target program adheres to the syntax “[program] [args] [input file]”. Both of these limitations can be easily worked around. The code is hardly what I’d call production-ready, but it gets the job done.<\/p>\n
You can download FuzzDiff here:<\/p>\n