full-disclosure - Re: Exploiting buffer overflows via protected GCC

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20090216140621.GA19621@suse.de>
Date: Mon, 16 Feb 2009 15:06:21 +0100
From: Marcus Meissner <meissner@...e.de>
To: ArcSighter Elite <arcsighter@...il.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: Exploiting buffer overflows via protected GCC

On Mon, Feb 16, 2009 at 09:00:33AM -0500, ArcSighter Elite wrote:
> James Matthews wrote:
> > I would recommend doing the following things.
> > 
> > 1. Ask on the Ubuntu GCC list what protection is implemented. (Or just look
> > at the source)
> > 2. Use GCC to see where the execution is being redirected and so you can
> > have a better visual of whats going on.
> > 3. Are you sure the stack is executable?

_fortify_fail is caused by the light weight buffer overflow checking,
enabled by the -D_FORTIFY_SOURCE=2 compile time flag.

Ciao, Marcus

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