Internet Explorer 8 introduces some major architectural changes, called "Loosely Coupled IE" (LCIE). LCIE separates the main window process (frame process) from the processes hosting the different web applications in different tabs (tab processes). A frame process can create multiple tab processes, each of which can be of a different integrity level; each tab process can host multiple web sites. The processes use asynchronous Inter-Process Communication to synchronize themselves. Generally, there will be a single frame process for all web sites. In Windows Vista with Protected Mode turned on, however, opening privileged content (such as local HTML pages) will create a new tab process as it will not be constrained by Protected Mode.
Internet Explorer exposes a set of Component Object Model (COM) interfaces that allow other components to extend the functionality of the browser. Extensibility is divided into two types: Browser extensibility and Content extensibility. The browser extensibility interfaces can be used to plug in components to add context menu entries, toolbars, menu items or Browser Helper Objects (BHO). BHOs are used to extend the feature set of the browser, whereas the other extensibility options are used to expose the feature in the UI. Content extensibility interfaces are used by different content-type handlers to add support for non-native content formats. BHOs not only have unrestricted access to the Internet Explorer DOM and event model, they also can access the filesystem, registry and other OS components. Content extensibility can be either in terms of "Active Documents" ("Doc Objects") (e.g., SVG or MathML) or "ActiveX controls". ActiveX controls are used for content handlers that render content embedded within an HTML page (e.g., Adobe Flash or Microsoft Silverlight). Doc objects are used when the content type will not be embedded in HTML (e.g., Microsoft Word, PDF or XPS). In fact, the Trident rendering engine is itself exposed as a Doc object, so HTML in itself is treated as an Active Document.
Internet Explorer add-on components run with the same privileges as the browser itself, unlike client-side scripts that have a very limited set of privileges. Add-ons can be installed either locally, or directly by a web site. Since the add-ons have a more privileged access to the system, malicious add-ons can and have been used to compromise the security of the system. Internet Explorer 6 Service Pack 2 onwards provide various safeguards against this, including an Add-on Manager for controlling ActiveX controls and Browser Helper Objects and a "No Add-Ons" mode of operation as well as greater restrictions on sites installing add-ons.
Internet Explorer itself can be hosted by other applications via a set of COM interfaces. This can be used to embed the browser functionality inside the application. Also, the hosting application can choose to host only the MSHTML.dll rendering engine, rather than the entire browser.
Internet Explorer uses a zone-based security framework that groups sites based on certain conditions, including whether it is an Internet- or intranet-based site as well as a user-editable whitelist. Security restrictions are applied per zone; all the sites in a zone are subject to the restrictions.
Internet Explorer 6 SP2 onwards uses the "Attachment Execution Service" of Microsoft Windows to mark executable files downloaded from the Internet as being potentially unsafe. Accessing files marked as such will prompt the user to make an explicit trust decision to execute the file, as executables originating from the Internet can be potentially unsafe. This helps in preventing accidental installation of malware.
Internet Explorer 7 introduced the phishing filter, that restricts access to phishing sites unless the user overrides the decision. With version 8, it also blocks access to sites known to host malware. Downloads are also checked to see if they are known to be malware-infected.
In Windows Vista, Internet Explorer by default runs in what is called "Protected Mode", where the privileges of the browser itself are severely restricted - it cannot make any system-wide changes. One can optionally turn this mode off but this is not recommended. This also effectively restricts the privileges of any add-ons. As a result, even if the browser or any add-on is compromised, the damage the security breach can cause is limited.
Patches and updates to the browser are released periodically and made available through the Windows Update service, as well as through Automatic Updates. Although security patches continue to be released for a range of platforms, most feature additions and security infrastructure improvements are only made available on operating systems which are in Microsoft's mainstream support phase.
On December 16, 2008, Trend Micro recommended users switch to rival browsers until an emergency IE patch was released to fix a potential security risk which "could allow outside users to take control of a person's computer and steal their passwords". Microsoft representatives countered this recommendation, claiming that "0.02% of internet sites" were affected by the flaw.
On December 17, 2008, a fix to the security problem above became available, with the release of the Security Update for Internet Explorer KB960714, which is available from Microsoft Windows Update's webpage. Microsoft has said that this update fixes the security risk found by Trend Micro the previous day.
Internet Explorer has been subjected to many security vulnerabilities and concerns: Much of the spyware, adware, and computer viruses across the Internet are made possible by exploitable bugs and flaws in the security architecture of Internet Explorer, sometimes requiring nothing more than viewing of a malicious web page in order to install themselves. This is known as a "drive-by install". There are also attempts to trick the user into installing malicious software by misrepresenting the software's true purpose in the description section of an ActiveX security alert.
A number of security flaws affecting IE originated not in the browser itself, but ActiveX-based add-ons used by it. Because the add-ons have the same privilege as IE, the flaws can be as critical as browser flaws. This has led to the ActiveX-based architecture being criticized for being fault-prone. By 2005, some experts maintained that the dangers of ActiveX have been overstated and there were safeguards in place. In 2006, new techniques using automated testing found more than a hundred vulnerabilities in standard Microsoft ActiveX components. Security features introduced in then recently released Internet Explorer 7 mitigated some of these vulnerabilities.
Internet Explorer in 2008 had a number of published security vulnerabilities. According to research done by security research firm Secunia, Microsoft did not respond as quickly as its competitors in fixing security holes and making patches available. The firm also reported 366 vulnerabilities in ActiveX controls, an increase from the prior year.
According to the latest information, Secunia reports that IE6 has 24 known unpatched vulnerabilities, IE7 has 11, and IE8 has 4. The most severe unpatched Secunia advisories affecting Microsoft Internet Explorer 6.x, 7.x, and 8.x with all vendor patches applied, are all rated Extremely critical. The oldest known unpatched vulnerabilities for IE6, IE7, and IE8 date from November 7, 2003, June 6, 2006, and February 26, 2007 respectively.
According to the latest information, security research firm SecurityFocus reports that IE6 has 396 known unpatched vulnerabilities, IE7 has 22, and IE8 has 25. The oldest known unpatched vulnerabilities for IE6, IE7, and IE8 date from November 20, 2000, May 17, 2007, and April 11, 2009 respectively.