full-disclosure - Re: Windows Command Processor CMD.EXE Buffer Overflow

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: <242a0a8f0610230954m2de02619s5dd9bb592578b555@mail.gmail.com>
Date: Mon, 23 Oct 2006 12:54:29 -0400
From: "Brian Eaton" <eaton.lists@...il.com>
To: full-disclosure <full-disclosure@...ts.grok.org.uk>
Subject: Re: Windows Command Processor CMD.EXE Buffer
	Overflow

On 10/23/06, offset@...vanet.com <offset@...vanet.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?

Regards,
Brian

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