Hi, thanks for the report, but we don't consider this a security bug, as exploiting it would require access to write to system32. If you have write access to that directory, you are already strictly more powerful than Chrome.

The issue is aggravated on Windows 7 because the DLL is not present, resulting in an exploitable DLL Hijack vulnerability, even tho the SafeDllSerchMode flag is enabled.

I have tested on 3 distinct Windows 7 installations, and none of them ship the atlthunk.dll. I cant confirm why or on what circumstances the dll is/isnt available on Windows 7. But a patch to the LoadLibrary call should mitigate the issue on the vulnerable scenarios.

Usually dll hijacking attacks require (low) access to the machine.

If a low privileged user is infected, a malware is capable of injecting code into chrome process.

Hi, like we mentioned, we do not consider DLL hijacking to be a vulnerability in Chrome. See https://www.chromium.org/Home/chromium-security/security-faq#TOC-Why-aren-t-physically-local-attacks-in-Chrome-s-threat-model- for some more details behind this point of view.