[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Full-disclosure] Windows Command Processor CMD.EXE Buffer Overflow
- To: full-disclosure@xxxxxxxxxxxxxxxxx
- Subject: Re: [Full-disclosure] Windows Command Processor CMD.EXE Buffer Overflow
- From: offset@xxxxxxxxxxxx
- Date: Mon, 23 Oct 2006 16:21:14 +0000 (UTC)
This works on Windows SP2 : The system doesn't reply "The filename or extension
is too long."
but cmd crash.
----- Tillmann Werner <tillmann.werner@xxxxxx> 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/