mailing list archives
Re: Windows Command Processor CMD.EXEBufferOverflow
From: "Dave \"No, not that one\" Korn" <davek_throwaway () hotmail com>
Date: Wed, 25 Oct 2006 14:09:14 +0100
Peter Ferrie wrote:
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
Can't think of a witty .sigline today....
Full-Disclosure - We believe in it.
Hosted and sponsored by Secunia - http://secunia.com/
Re: Windows Command Processor CMD.EXE Buffer Overflow Nick FitzGerald (Oct 23)