Full Disclosure mailing list archives

Re: Windows Command Processor CMD.EXE Buffer Overflow

From: Tillmann Werner <tillmann.werner () gmx de>
Date: Mon, 23 Oct 2006 18:07:04 +0200

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/

Current thread:

Re: Windows Command Processor CMD.EXE Buffer Overflow Luis Alberto Cortes Zavala (Oct 20)
- Re: Windows Command Processor CMD.EXE Buffer Overflow Tillmann Werner (Oct 23)
  - Re: Windows Command Processor CMD.EXE Buffer Overflow Arnaud Jacques (Oct 23)
  - Re: Windows Command Processor CMD.EXE Buffer Overflow C. Hamby (Oct 23)
    - Re: Windows Command Processor CMD.EXE Buffer Overflow David Taylor (Oct 23)