full-disclosure - Re: Fuzzing and SEH

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Thu, 04 Nov 2010 13:05:43 -0500
From: Marsh Ray <marsh@...endedsubset.com>
To: primehaxor <primehaxor@...il.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: Fuzzing and SEH

On 11/04/2010 06:30 AM, primehaxor wrote:
> Hi list,
>
> When i run some fuzzing tests i can't trap the exception when found some
> bug due invalid input. I'm trying to figure out a smart way to handle
> the exception, and tell me when it run.

Your question lacks specifics.

> On the PoC i've got the daemon crashed but it still working whithout
> response the requests.

For example, you use the term "SEH" in the title which implies an MS 
Windows environment, now you're talking about a "daemon" which usually 
implies a Unix environment.

> I'm reading the Sulley framework and PyDBG doc to find some trick to get
> it working.
>
> Any ideia?

Uhh, set a breakpoint on the exception (or its handler)?  I don't know 
the specific tools you mention, but it's pretty basic debugger 
functionality.

- Marsh

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/