driller
driller copied to clipboard
shellphish
Driller: augmenting AFL with symbolic execution!
Hi, all. I want to test the driller with a program that reads a file, like djpeg. First, I want to test a very simple example, ```c #include #include #include...
Hello guys, I need some help. I have some question about driller want to ask. First, I followed the example https://github.com/shellphish/driller#example to run the driller. I print the `new_inputs`, and...
When I run driller to test one of cgc binary named NRFIN_00017 with the command "shellphuzz -c 2 -d 2 -C NRFIN_00017 ", I get the following error, could you...
When testing program with AFL , the program must read a file as an input , thus AFL can do the mutation job with the input file. While driller‘s test...
As described in the title, driller fails to generate the new inputs for the following toy program (please remove `.txt` from all files, `hello.txt` is the binary). If you compile...
In the architecture of Driller, AFL component is augmented by angr. And generally only one path is investigated by the angr component at a time, contrary to purely utilizing angr...
Hello, I have been using driller. I look into the schedule of celery, but there is one question confusing me. When driller generates new inputs, it will pass the new...
Hi, guys When running the afl-cgc, it puzzles me very much that what parameter should I set for the varialbe driller_path, which means the the location of driller executable. Is...
I test driller by the example `import driller d = driller.Driller("./CADET_00001", # path to the target binary "racecar", # initial testcase "\xff" * 65535, # AFL bitmap with no discovered...
I'm back, and this time I'm drilling a binary which doesn't need any LD_PRELOAD junk, it's just a normal executable. This time I eventually get what looks to be a...
Metadata
Owner
Metadata
Driller: augmenting AFL with symbolic execution!