mailing list archives
Re: Windows Command Processor CMD.EXE Buffer Overflow
From: "Brian Eaton" <eaton.lists () gmail com>
Date: Mon, 23 Oct 2006 12:54:29 -0400
On 10/23/06, offset () galvanet com <offset () galvanet com> wrote:
This works on Windows SP2 : The system doesn't reply "The filename or extension is too long."
but cmd crash.
Is there a reason that a buffer overflow in cmd.exe matters?
If the attacker is sending arbitrary input to cmd.exe, haven't they
owned the box anyway?
Full-Disclosure - We believe in it.
Hosted and sponsored by Secunia - http://secunia.com/
Re: Windows Command Processor CMD.EXE Buffer Overflow Nick FitzGerald (Oct 23)