[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <453CEE70.9030409@gci.net>
Date: Mon, 23 Oct 2006 08:31:44 -0800
From: "C. Hamby" <fixer@....net>
To: Tillmann Werner <tillmann.werner@....de>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: Windows Command Processor CMD.EXE
Buffer Overflow
This looks more like the command processor itself is reporting an error
because of length. The %COMSPEC% variable is kind of an odd thing to
use if the shell is already open (you usually see that in VBS to call
the current command shell followed by the /K to keep it open). Then
again I could be totally wrong....it does happen from time to time :-)
I agree with Tillman, this doesn't look like a security issue.
-cdh
Tillmann Werner wrote:
> Luis,
>
>> Tried it on Win2k3 SP1:
>> C:\Documents and Settings\Administrator>%COMSPEC% /K
>> "dir\\?\AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
>> AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
>> A AAAA
>> AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
>> A AAAA
>> AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA"
>> System replied:
>> The filename or extension is too long.
>>
>>
>> YEah! Buffer Overflow Windows XP SP2
>>
>> I Hill debug this.
>
> What makes you think there is a buffer overflow? I'd say the 'dir' command
> reports an error for parameters beyond 256 chars. Just plain error handling,
> not a security issue, or am I missing something?
>
> Tillmann
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.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/
Powered by blists - more mailing lists