You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which version of Visual Studio are you building with (if any)?
N/A
Which version of the WiX Toolset Visual Studio Extension are you building with (if any)?
N/A
Which version of .NET are you building with?
N/A
If the problem occurs when installing your packages built with WiX, what is the version of Windows the package is running on?
(Windows version)
Describe the problem and the steps to reproduce it.
Malicious software can monitor the Temp folder and quickly insert a DLL into the clean room folder to DLL hijack the Burn engine there. Thus, if a bundle is launched by the user elevated (such as Right click ->Run as administrator or launched from elevated command-prompt) the hijacking DLL will also be elevated.
Describe the behavior you expected and how it differed from the actual behavior.
Elevated bundles in the user context should not be able to be DLL hijacked.
The text was updated successfully, but these errors were encountered:
To prevent DLL hijacking the clean room process when launched elevated,
the system Temp folder will be used instead of the user's temp folder.
This ensures the user cannot slip malicious DLLs into the clean room.
Fixeswixtoolset/issues#5724
robmen
added a commit
to wixtoolset/wix3
that referenced
this issue
Nov 18, 2017
To prevent DLL hijacking the clean room process when launched elevated,
the system Temp folder will be used instead of the user's temp folder.
This ensures the user cannot slip malicious DLLs into the clean room.
Fixeswixtoolset/issues#5724
The text was updated successfully, but these errors were encountered: