Peter wrote: > Perhaps you should read about it on Microsoft's site. > It's not a buffer overflow. WMF files since at least Windows > 3.0 days have been allowed to carry executable code in the > form of their own SetAbortProc handler. This is perfectly > legitimate, though the design is a poor one. The only thing > that has changed is the code that is being executed.
You are correct, that was my oversight in typing (minus the thinking). No bufferoverflow ;) -Todd _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
