full-disclosure - Re: ShortNotes : Stack Smashing with GCC4

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>] [day] [month] [year] [list]

Message-ID: <1681f2df0704201158h7674fe2dqa65fb6cb31e5c224@mail.gmail.com>
Date: Fri, 20 Apr 2007 14:58:34 -0400
From: "Chris Rohlf" <chris.rohlf@...il.com>
To: full-disclosure@...ts.grok.org.uk
Cc: xwings@...urity.net.my
Subject: Re: ShortNotes : Stack Smashing with GCC4

Your section:

> ** [ iv. call %edx ] **

Was also covered here some time ago.

http://www.milw0rm.com/papers/70

(I am only running gcc 4.0.3) In main() %edx is pointing to the start
of your environment variables, not the stack. If you were to call
another function from main() it would probably no longer point there.
So maybe this technique works for vulnerablilities in programs parsing
command line arguments in main() but its very limited in its use.

chris

-- 

http://em386.blogspot.com

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