[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Full-disclosure] Windows Command Processor CMD.EXEBufferOverflow
- To: full-disclosure@xxxxxxxxxxxxxxxxx
- Subject: Re: [Full-disclosure] Windows Command Processor CMD.EXEBufferOverflow
- From: "Dave \"No, not that one\" Korn" <davek_throwaway@xxxxxxxxxxx>
- Date: Wed, 25 Oct 2006 14:09:14 +0100
Peter Ferrie wrote:
>>> 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.
No it doesn't. It passes arbitrary data to the windows gui shell exec
function. It doesn't invoke cmd.exe. Unless you have an actual working
example?
cheers,
DaveK
--
Can't think of a witty .sigline today....
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/