DLL hijacking problem

Lee ler762@gmail.com
Sat Aug 28 17:30:00 GMT 2010

On 8/28/10, Corinna Vinschen wrote:
> On Aug 28 09:36, Lee wrote:
>> On 8/28/10, Corinna Vinschen wrote:
>> > On Aug 28 08:35, Lee wrote:
>> >> Would cygwin1.dll still be loaded from the directory from which the
>> >> application loaded or would I have to put a copy of cygwin1.dll into
>> >> whatever GetSystemDirectory resolves to?
>> >
>> > Copying cygwin1.dll to the system directory was never correct, contains
>> > to be so, and has nothing to do with the actual DLL hijacking problem.
>> Sorry - I thought an example of the DLL hijacking problem was if I had
>> extension "foo" registered to be [processed? loaded?] by foo.exe and I
>> doubleclicked on "datafile.foo" in windows explorer.
> The security problem is not about DLLs in the same dir as the EXE, it's
> about the CWD which is in the DLL search path.

If I double-click on "Z:\datafile.foo" in windows explorer then
CWD="Z:\" - correct?
And if double-clicking on a data file launches a program that was
build with cygwin, and cygwin1.dll gets loaded from the same directory
as the program - even after this patch is applied - then none of my
stuff breaks & I'm a happy camper :)


More information about the Cygwin-developers mailing list