10:03 <tihmstar> by "fuzzing a file" we (at least i) mean modifying a file, basically randomly changing some bits
10:04 <tihmstar> we
have a tool called zzuf which modifys the file for you, but since
obvously there is a very low change to make MSafari crash by modifying
some bytes we need to do it again and again
10:04 <tihmstar> therefore smart people around here (me included :P ) createt scripts/tools to automate this process
10:06 <JBUni> is
it possible to insert syscalls in the form of hex, and have the kernel
read those and redirect to a different part of memory, etc?
10:07 <tihmstar> then
you can start looking at the bug hoping you can let it do something
more like just crasjing the process, like inserting malcious code
10:08 <tihmstar> looking
at fuzzycactus for example: you give it a mov file and it automatically
does following things in a loop (until the device crashes): creates a
fuzzed file with zzuf, opens that file in mobilesafari, waits some time,
kills safari and the loop starts from beginning obviuosly the new
fuzzed file is different than the one before
10:09 <JBUni> but with a program that runs randomly like this, you're unable to keep proper track of which bugs happened
10:11 <tihmstar> it
also pairs the crash to the mov file caused the crash and to the
parameters were sent to zzuf to be able to recreate the file (which you
actually don't need since it also copies you the fuzzed file to the dir)
10:11 <tihmstar> if you have a really good crash we are interested in your fuzzed mov file AND your original file
10:12 <tihmstar> in this case send both files and the crashlog to crakun (i think his mail was crakun@m0bdev.com but im not quite sure)
