search

Bit9 / sulley

A pure-python fully automated and unattended fuzzing framework.
GNU General Public License v2.0
12 stars 5 forks source link

Sulley not restarting properly after finding an exploit #3

Closed ghost closed 11 years ago

ghost commented 11 years ago

Hi,

This is an issue that I am having with both Bit9's Sulley and OpenRCE's Sulley. When I am fuzzing with Sulley, I set up the process monitoring and network monitoring agents on the target computer, and then start fuzzing the target from the host computer. This works fine until I hit an exploit. When I find an exploit and it crashes the program on the target computer, the process monitor properly restarts the program, but, for some reason, the Sulley fuzzer on the host computer does not restart properly. It says "restarting target process" --> then I see that the target process HAS restarted properly on the target computer, but then the host computer says "Restarting the target failed, exiting". Here is a sample of what I have been seeing from running Sulley on both ubuntu and windows:

[2013-06-06 09:54:07,702] [ERROR] -> fuzzed 0 of 5620 total cases [2013-06-06 09:54:07,703] [ERROR] -> fuzzing 12 of 5620 [2013-06-06 09:54:10,121] [ERROR] -> xmitting: [1.12] [2013-06-06 09:54:10,127] [WARNING] -> Nothing received on socket. [2013-06-06 09:54:10,128] [WARNING] -> sleeping for 0.000000 seconds [2013-06-06 09:54:10,332] [ERROR] -> netmon captured 1671 bytes for test case #12 [2013-06-06 09:54:10,535] [ERROR] -> procmon detected access violation on test case #12 [2013-06-06 09:54:10,535] [ERROR] -> primitive lacks a name, type: delim, default value: [2013-06-06 09:54:10,736] [ERROR] -> [INVALID]:20202020 Unable to disassemble at 20202020 from thread 7532 caused access violation [2013-06-06 09:54:10,737] [WARNING] -> restarting target process [2013-06-06 09:54:15,941] [CRITICAL] -> Restarting the target failed, exiting. ##Even though I know it restarted correctly

**Also I have always just ignored the "ERROR" and "WARNING" messages because the fuzzing has been working.

To get around this on windows I wrote a batch script to just restart automatically, but then after restarting 2-3 times, the program would start to freeze on the "Restarting the target failed, exiting" step. So then I would have to force quit and start it up again. The same thing happened when I made a shell script to just restart the program continuously on ubuntu.

Any ideas?

Thanks a lot, 4leaf

magwitch324 commented 11 years ago

Hey I will definitely take a look but probably tomorrow. the thing that will help me most is the dump from your process monitor with log level of 5.

Thanks for finding this bug.

Magwitch

magwitch324 commented 11 years ago

@4leafclovrs is this still an issue for you? if not I am going to close this issue.

magwitch324 commented 11 years ago

I am closing this issue. if you still need help with it you can reopen it.