full-disclosure - Re: 18th anniversary of Internet worma.k.a. Morris worm

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]

Message-Id: <200611121837.kACIbq8c032522@turing-police.cc.vt.edu>
Date: Sun, 12 Nov 2006 13:37:52 -0500
From: Valdis.Kletnieks@...edu
To: "Dave \"No, not that one\" Korn" <davek_throwaway@...mail.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: 18th anniversary of Internet worma.k.a.
	Morris worm

On Sun, 12 Nov 2006 18:21:16 GMT, "Dave \"No, not that one\" Korn" said:
> Georgi Guninski wrote:
> > my question was:
> >
> > when was the first provable *public* (as in common sense)
> > announcement of the exploitability of buffer overflows.
> 
>   The use of smashing the stack to seize control of the program flow was in 
> everyday usage on the Commodore PET from around 1979-1980ish.  It was our 
> standard technique for making programs autorun after loading!

Was that a "classic" smash-the-stack, where an overly long paramater is used
to over-write the return pointer, or were you guys just intercepting the
return pointer directly?  If the latter, I'm pretty sure there was software
that would overlay return pointers in order to redirect program flow as far
back as IBM's OS/360 in the 1967-75 timeframe.

Content of type "application/pgp-signature" skipped

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