Image
 
linkedin_logo.png rss_logo.jpg
twitter_logo.png youtube_logo.jpg
Latest Additions
 
EH-Net Login
Welcome Guest.






Lost Password?
No account yet? Register
Who's Online
We have 29 guests online
 
Advertisement

You are here: Home arrow Resourcesarrow Tutorialsarrow Fuzzing with Fuzzers
EH-Net
May 24, 2013, 02:32:27 PM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Go back to The Ethical Hacker Network Online Magazine Home Page
 
   Home   Help Calendar Login Register  
Pages: [1]   Go Down
  Print  
Author Topic: Fuzzing with Fuzzers  (Read 8417 times)
0 Members and 1 Guest are viewing this topic.
Dertweiller
Newbie
*
Offline Offline

Posts: 3


View Profile
« on: May 20, 2007, 03:59:47 PM »

Hi there,

I was wondering if anyone knew where I could get information on "A how-to giude on Fuzzing Applications"? If you do know, can you please send me a link?

Thanks

Dertweiller
Logged
goAci
Newbie
*
Offline Offline

Posts: 2


View Profile
« Reply #1 on: July 12, 2007, 04:54:15 AM »

Hi there,

I was wondering if anyone knew where I could get information on "A how-to giude on Fuzzing Applications"? If you do know, can you please send me a link?

Thanks

Dertweiller
what exactly does "Fuzzing Application" mean?
tia
Logged
What90
Full Member
***
Offline Offline

Posts: 120


View Profile WWW
« Reply #2 on: July 12, 2007, 06:06:13 AM »

Fuzzing is a software testing technique where you supply a program with faulty or randomized data in place of its normally expected input.

Here's some more to read on it:

http://reddevnews.com/techbriefs/article.aspx?editorialsid=261

http://appliedsec.com/resources.html

Playing with Ruby to build a fuzzer framework:
http://www.devx.com/security/Article/33559
Logged

don
Editor-In-Chief
Administrator
Hero Member
*****
Offline Offline

Posts: 4168


Editor-In-Chief


View Profile WWW
« Reply #3 on: July 12, 2007, 10:08:52 AM »

I just got a review copy of:

[/b]]Fuzzing - Brute Force Vulnerability Discovery

By Michael Sutton, Adam Greene and Pedram Amini (Foreword by H.D. Moore)

Haven't read it yet, so I can't comment fully, but it's worth a look.

Don
Logged

CISSP, MCSE, CSTA, Security+ SME
Kev
Guest
« Reply #4 on: July 15, 2007, 12:38:15 PM »

Fuzzing is an important part of looking for vulnerabilities. Spike still seems to be the popular fuzzer.  Many people think writing your own exploit code is extremely difficult and you must be a programming wiz.  Thats no longer true since the advent of fuzzers.  You do need to understand windows memory and cpu registries and some assembly instructions. You dont really need to write a lot of code because there exists well written shell code that you can just copy and paste and edit as needed !

You find an app that you want to test and then run it. Run a debugger and then your fuzzer.  If the program crashes, your in luck. At that point you begin to  review your debugger and look for cpu registries after the crash. Find the area where you can insert your shell and create your exploit. You're  trying to push the buffer to except your code. Well, there is a bit more to it than that but most of it is really just understanding things like binary trees and there are auto scripts available to help with this. Your basically looking for the address to insert your shell code.  If you understand where to point your shell code, you can just about copy and paste everything and then edit it to point where it needs to go.

This is all depends on the program having vulnerable code and the its getting harder to find really easily exploitable programs. If you are starting to learn you should find an old version of a program and play with it, one that was known for having a lot of holes.   Once you do find that you have found an exploit that works and is stable, its like finding gold. Its an awesome feeling.  Of course you have to remember that many others are out there testing the same software with the same fuzzer if you are using Spike so dont think you are the only one with that exploit, lol.   It eventually gets out because people are always trading their exploits to get others or they have to brag ,etc and the vulnerable code is corrected sooner or later, which is good.     
« Last Edit: July 15, 2007, 01:23:36 PM by Kev » Logged
Kev
Guest
« Reply #5 on: July 15, 2007, 02:45:14 PM »

One other thought I forgot to post is there is another good reason to become good at fuzzing.  It is only going to get more and more competitive in the world of security as more  people get attracted to this line of work.  If you can show you created your own exploit against a vulnerable program, its going to set you miles above most other applicants. 
Logged
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines
Joomla Bridge by JoomlaHacks.com
Valid XHTML 1.0! Valid CSS!
Page created in 0.068 seconds with 23 queries.
 
Exclusive Deal

sansfire13_245x90_cw90.jpg
SANSFIRE 2013
June 15 - 22

5% Off w/ Code: EHN_5

SANS Deals 4 EH-Netters
5% OFF Any SANS Course in Any Format!
Coupon Code: EHN_5 Including SANS Rocky Mountain 2013 & SANS Boston 2013
Polls
Compared to this year, 2013 will be:
 
Recent Forum Topics
EH-Net News Feeds
Latest Additions
 
         
Advertisement

© 2013 The Ethical Hacker Network
Joomla! is Free Software released under the GNU/GPL License.