[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Full-disclosure] Windows Command Processor CMD.EXE BufferOverflow

To: "full-disclosure" <full-disclosure@xxxxxxxxxxxxxxxxx>
Subject: Re: [Full-disclosure] Windows Command Processor CMD.EXE BufferOverflow
From: "Peter Ferrie" <pferrie@xxxxxxxxxxxx>
Date: Mon, 23 Oct 2006 14:58:18 -0700

> > file://
> > ?
> 
> OK, I'll bite.  Why are file:// URLs relevant to the discussion?

It allows arbitrary data to be passed to CMD.EXE, without first owning the 
system.

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

Follow-Ups:
- Re: [Full-disclosure] Windows Command Processor CMD.EXE BufferOverflow
  - From: Matthew Flaschen
- Re: [Full-disclosure] Windows Command Processor CMD.EXE BufferOverflow
  - From: Brian Eaton
- Re: [Full-disclosure] Windows Command Processor CMD.EXEBufferOverflow
  - From: Dave \"No, not that one\" Korn

References:
- Re: [Full-disclosure] Windows Command Processor CMD.EXE Buffer Overflow
  - From: Brian Eaton

Prev by Date: Re: [Full-disclosure] Windows Command Processor CMD.EXE Buffer Overflow
Next by Date: Re: [Full-disclosure] Windows Command Processor CMD.EXE BufferOverflow
Previous by thread: Re: [Full-disclosure] Windows Command Processor CMD.EXE Buffer Overflow
Next by thread: Re: [Full-disclosure] Windows Command Processor CMD.EXE BufferOverflow
Index(es):
- Date
- Thread