Moreover, many of the listed applications are still actively being developed to this day, such as Skype, Maxthon, Sleipnir, SlimBrowser, WebbIE, Steam client, & Winamp (community update build). Meanwhile, others like SlimBrowser (initial release: Dec 2012) & UltraBrowser (initial release: Sep 2009) did not exist during the Windows 2000 era. The aforementioned Wiki entry is meant to be a historical record, so some of the listed applications are old. That list is old, from the Windows 2000 era. So perhaps it’s only a matter of time before malicious actors come up with payloads that target Win Explorer & IE-dependent applications. PS: In Win 7, Windows Explorer (which uses IE’s binaries) works just fine with IE “turned off” (ie.
Here’s a non-exhaustive list of 3rd-party web browsers & non-browser applications that use IE for various purposes. The user can no longer launch it, but its web browser engine remains operational for applications that use it. Starting with Windows 2000, it is possible to disable Internet Explorer. That being said, to avoid a false sense of security … As such, with the system’s “default” IE being disabled from launching, it is impossible for any malicious hyperlink to open any web browser w/o triggering a “ Windows can’t open this file” prompt. I use portable 3rd-party web browsers, & to prevent registry entries, I do NOT set any browser as default. IE’s shortcut links via the START menu search.C:\Program Files (x86)\Internet Explorer\iexplore.exe.C:\Program Files\Internet Explorer\iexplore.exe.in fact, the following items disappear from view:. After a reboot, it is no longer possible to launch IE in any way. NET implementation of JScript) ? Is it vulnerable to the latest zero-day remote code execution vulnerability ?Īnother precautionary measure I’d taken is to disable the IE browser via ‘ Turn Windows Features on or off‘. Since I use portable 3rd-party media players, I’m fine with leaving jscript.dll in its restricted crippled state.īut what about (basically the the. removing SYSTEM user’s permissions from IE’s 32/64-bit jscript.dll- will break the respective 32/64-bit Windows Media Player in Win 7.Ĭlicking on any video/audio file will lead to the “ Server execution failed” error, while clicking wmplayer.exe will result in no response. For instance, the workaround recommended for mitigating the latest zero-day IE vulnerability - ie.
0 kommentar(er)
