New Framework Release
This release contains fixes for many of the bugs recently reported. Also, it includes a zip file containing the full source code.
As mentioned previously, please submit feature requests, bug reports, comments, etc to aportnoy [at] fuzzing.org
–
aaron
Last 5 posts by aportnoy
- Post Vegas Update - August 8th, 2007
10 Comments so far
Leave a reply

its broken,
the default installation puts everything at C:\Program Files
also the uninstall.exe when clicking on it deteles everything in this folder!
THANKS ;)
ha
Awesome fuzzer, waiting for file fuzzing capabilities.
Thanks for making it public!
yes a very good fuzzer, but codenomicon is quite better, but has a another “method”, anyway. great work.
nice TODO list! ;)
@bruter:
The default installation directory is C:\Program Files\Sulley Fuzzing Framework. The 2nd page of the installer allows you to change that.
For some odd reason, on Windows 2000 it appears as though the installer defaults to C:\Program Files (although you *can* still easily change that on the 2nd page). I’m trying to see if this is a known problem with NSI and I’ll post any findings when I discover them.
With regard to the uninstaller, it simply removes the installation directory… so, you’ll definitely want to specify something other than C:\Program Files ;)
UPDATE: I’ve uploaded a new installer (overwrote the old one on the main page). Apparently Windows 2k/2k3 differs from XP in what is stored in the registry about the program files directory. Anyway, the new version defaults to the correct directory.
@yes:
how exactly is codenomicon better? Is it the lack of target monitoring (besides sending a protocol “ping”) you like? Extending sulley to write up all protocol mutations to numbered files is a simple but imho meaningless task, hey presto, codenomicon.
Any updates to Sulley?
Hi,
I tried executing simultaneous fuzzing of multiple targets in the same session using :
sess = sessions.session(session_filename=”C:\\testing.txt”)
target = sessions.target(”127.0.0.1″, 80)
target2 = sessions.target(”127.0.0.1″, 523)
target.netmon = pedrpc.client(”127.0.0.1″, 26001)
target2.netmon = pedrpc.client(”127.0.0.1″, 26004)
target.procmon = pedrpc.client(”127.0.0.1″, 26002)
target2.procmon = pedrpc.client(”127.0.0.1″, 26005)
sess.add_target(target1)
sess.add_target(target2)
sess.connect(s_get(”HTTP”))
sess.fuzz()
I had the netmons for target1 and target2 set to port 26002 & 26005 respectively and the procmons set to 26001 & 26004 ports respectively. However, during execution only one process gets fuzzed at a time. Is there something missing? Both these ports had HTTP servers running as can be seen from TCPView and ProcessExplorer tools from sysinternals.
Yes, any updtes to sulley? python 2.5? pedram, please stop goofing off and update paimei, pydbg and sulley to work with a recent copy of python, as it is now you need multiple virtual machines to work with all the tools.
@wang et al:
There are updates available to both PaiMei and Sulley and both work with Python 2.5. I simply don’t have the time (or skills) to create fancy installers so both have only been available via SVN for some time:
http://code.google.com/p/paimei/
http://code.google.com/p/sulley/
-pedram
lol, less playing with USB powered missile launchers and more coding :)
Sulley is great btw - thanks.