Jump to content

Browser security: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Bender the Bot (talk | contribs)
Bots
1,008,858 edits
m →‎Security: HTTP→HTTPS for Ars Technica, per BRFA 8 using AWB
Rescuing 2 sources and tagging 0 as dead. #IABot (v1.5beta)
Line 12: Line 12:
The browser may not be aware of any of the breaches above and may show user a safe connection is made.
The browser may not be aware of any of the breaches above and may show user a safe connection is made.


Whenever a browser communicates with a website, the website, as part of that communication, collects some information about the browser (in order to process the formatting of the page to be delivered, if nothing else).<ref>{{cite web | url=http://oreilly.com/catalog/httppr/chapter/http_pkt.html | title=HTTP Transactions | author=Clinton Wong | publisher=O'Reilly}}</ref> If malicious code has been inserted into the website's content, or in a worst-case scenario, if that website has been specifically designed to host malicious code, then vulnerabilities specific to a particular browser can allow this malicious code to run processes within the browser application in unintended ways (and remember, one of the bits of information that a website collects from a browser communication is the browser's identity- allowing specific vulnerabilities to be exploited).<ref>{{cite web | url=http://www.ebernieinc.com/9-ways-to-know-your-pc-is-infected-with-malware/ | title=9 Ways to Know Your PC is Infected with Malware}}</ref> Once an attacker is able to run processes on the visitor's machine, then exploiting known security vulnerabilities can allow the attacker to gain privileged access (if the browser isn't already running with privileged access) to the "infected" system in order to perform an even greater variety of malicious processes and activities on the machine or even the victim's whole network.<ref>{{cite web | url=http://www.symantec.com/security_response/whitepapers.jsp?inid=us_sr_flyout_publications_security | title=Symantec Security Response Whitepapers}}</ref>
Whenever a browser communicates with a website, the website, as part of that communication, collects some information about the browser (in order to process the formatting of the page to be delivered, if nothing else).<ref>{{cite web | url=http://oreilly.com/catalog/httppr/chapter/http_pkt.html | title=HTTP Transactions | author=Clinton Wong | publisher=O'Reilly | deadurl=yes | archiveurl=https://web.archive.org/web/20130613235658/http://oreilly.com/catalog/httppr/chapter/http_pkt.html | archivedate=13 June 2013 | df=dmy-all }}</ref> If malicious code has been inserted into the website's content, or in a worst-case scenario, if that website has been specifically designed to host malicious code, then vulnerabilities specific to a particular browser can allow this malicious code to run processes within the browser application in unintended ways (and remember, one of the bits of information that a website collects from a browser communication is the browser's identity- allowing specific vulnerabilities to be exploited).<ref>{{cite web | url=http://www.ebernieinc.com/9-ways-to-know-your-pc-is-infected-with-malware/ | title=9 Ways to Know Your PC is Infected with Malware}}</ref> Once an attacker is able to run processes on the visitor's machine, then exploiting known security vulnerabilities can allow the attacker to gain privileged access (if the browser isn't already running with privileged access) to the "infected" system in order to perform an even greater variety of malicious processes and activities on the machine or even the victim's whole network.<ref>{{cite web | url=http://www.symantec.com/security_response/whitepapers.jsp?inid=us_sr_flyout_publications_security | title=Symantec Security Response Whitepapers}}</ref>


Breaches of web browser security are usually for the purpose of bypassing protections to display [[pop-up advertising]]<ref name=mozilla-adblock-plus>{{cite web |url=https://addons.mozilla.org/firefox/addon/adblock-plus |title=Adblock Plus :: Add-ons for Firefox |authorlink=Wladimir Palant |first=Wladimir |last=Palant |work=[[Mozilla Add-ons]] |publisher=[[Mozilla Foundation]]}}</ref> collecting [[personally identifiable information]] (PII) for either [[Internet marketing]] or [[identity theft]], [[website tracking]] or [[web analytics]] about a user against their will using tools such as [[web bug]]s, [[Clickjacking]], [[Likejacking]] (where [[Facebook]]'s [[like button]] is targeted),<ref>{{cite news|url=http://www.cbc.ca/news/technology/story/2010/09/23/facebook-like-invitations.html|title=Facebook privacy probed over 'like,' invitations|date=23 September 2010|work=CBC News|accessdate=24 August 2011}}</ref><ref>{{cite news|url=http://www.pcmag.com/article2/0,2817,2391440,00.asp|title=German Agencies Banned From Using Facebook, 'Like' Button|last=Albanesius|first=Chloe|date=19 August 2011|work=[[PC Magazine]]|accessdate=24 August 2011}}</ref><ref name="cnet-privacy-scrutiny">{{cite news
Breaches of web browser security are usually for the purpose of bypassing protections to display [[pop-up advertising]]<ref name=mozilla-adblock-plus>{{cite web |url=https://addons.mozilla.org/firefox/addon/adblock-plus |title=Adblock Plus :: Add-ons for Firefox |authorlink=Wladimir Palant |first=Wladimir |last=Palant |work=[[Mozilla Add-ons]] |publisher=[[Mozilla Foundation]]}}</ref> collecting [[personally identifiable information]] (PII) for either [[Internet marketing]] or [[identity theft]], [[website tracking]] or [[web analytics]] about a user against their will using tools such as [[web bug]]s, [[Clickjacking]], [[Likejacking]] (where [[Facebook]]'s [[like button]] is targeted),<ref>{{cite news|url=http://www.cbc.ca/news/technology/story/2010/09/23/facebook-like-invitations.html|title=Facebook privacy probed over 'like,' invitations|date=23 September 2010|work=CBC News|accessdate=24 August 2011}}</ref><ref>{{cite news|url=http://www.pcmag.com/article2/0,2817,2391440,00.asp|title=German Agencies Banned From Using Facebook, 'Like' Button|last=Albanesius|first=Chloe|date=19 August 2011|work=[[PC Magazine]]|accessdate=24 August 2011}}</ref><ref name="cnet-privacy-scrutiny">{{cite news
Line 25: Line 25:
}}</ref><ref>{{cite web|ssrn=1717563|title=Facebook Tracks and Traces Everyone: Like This!|last=Roosendaal|first=Arnold|date=30 November 2010|accessdate=27 September 2011}}</ref> [[HTTP cookie]]s, [[zombie cookie]]s or [[Local shared object|Flash cookies]] (Local Shared Objects or LSOs);<ref name=mozilla-betterprivacy /> installing [[adware]], [[Computer virus|viruses]], [[spyware]] such as [[Trojan horse (computing)|Trojan horses]] (to gain access to users' [[personal computer]]s via [[Cracker (computer security)|cracking]]) or other [[malware]] including [[online banking]] theft using [[man-in-the-browser]] attacks.
}}</ref><ref>{{cite web|ssrn=1717563|title=Facebook Tracks and Traces Everyone: Like This!|last=Roosendaal|first=Arnold|date=30 November 2010|accessdate=27 September 2011}}</ref> [[HTTP cookie]]s, [[zombie cookie]]s or [[Local shared object|Flash cookies]] (Local Shared Objects or LSOs);<ref name=mozilla-betterprivacy /> installing [[adware]], [[Computer virus|viruses]], [[spyware]] such as [[Trojan horse (computing)|Trojan horses]] (to gain access to users' [[personal computer]]s via [[Cracker (computer security)|cracking]]) or other [[malware]] including [[online banking]] theft using [[man-in-the-browser]] attacks.


Vulnerabilities in the web browser software itself can be minimized by keeping browser software updated,<ref>{{cite web|url=http://itsecurity.vermont.gov/threats/web_attacks|title=Web Browser Attacks|author=State of Vermont|accessdate=11 April 2012}}</ref> but will not be sufficient if the underlying operating system is compromised, for example, by a rootkit.<ref>{{cite web|url=https://www.symantec.com/avcenter/reference/windows.rootkit.overview.pdf |title=Windows Rootkit Overview |publisher=Symantec |date= |accessdate=2013-04-20}}</ref> Some subcomponents of browsers such as scripting, add-ons, and cookies<ref>{{cite web|url=http://www.acunetix.com/websitesecurity/cross-site-scripting/|title=Cross Site Scripting Attack|accessdate=20 May 2013}}</ref><ref>{{cite web|url=http://blog.zeltser.com/post/2527547617/targeting-web-browser|title=Mitigating Attacks on the Web Browser and Add-Ons|author=Lenny Zeltser|accessdate=20 May 2013}}</ref><ref>{{cite web|url=https://arstechnica.com/security/2013/03/new-attacks-on-ssl-decrypt-authentication-cookies/|title=Two new attacks on SSL decrypt authentication cookies|author=Dan Goodin|accessdate=20 May 2013}}</ref> are particularly vulnerable ("the [[confused deputy problem]]") and also need to be addressed.
Vulnerabilities in the web browser software itself can be minimized by keeping browser software updated,<ref>{{cite web|url=http://itsecurity.vermont.gov/threats/web_attacks|title=Web Browser Attacks|author=State of Vermont|accessdate=11 April 2012|deadurl=yes|archiveurl=https://web.archive.org/web/20120213180056/http://itsecurity.vermont.gov/threats/web_attacks|archivedate=13 February 2012|df=dmy-all}}</ref> but will not be sufficient if the underlying operating system is compromised, for example, by a rootkit.<ref>{{cite web|url=https://www.symantec.com/avcenter/reference/windows.rootkit.overview.pdf |title=Windows Rootkit Overview |publisher=Symantec |date= |accessdate=2013-04-20}}</ref> Some subcomponents of browsers such as scripting, add-ons, and cookies<ref>{{cite web|url=http://www.acunetix.com/websitesecurity/cross-site-scripting/|title=Cross Site Scripting Attack|accessdate=20 May 2013}}</ref><ref>{{cite web|url=http://blog.zeltser.com/post/2527547617/targeting-web-browser|title=Mitigating Attacks on the Web Browser and Add-Ons|author=Lenny Zeltser|accessdate=20 May 2013}}</ref><ref>{{cite web|url=https://arstechnica.com/security/2013/03/new-attacks-on-ssl-decrypt-authentication-cookies/|title=Two new attacks on SSL decrypt authentication cookies|author=Dan Goodin|accessdate=20 May 2013}}</ref> are particularly vulnerable ("the [[confused deputy problem]]") and also need to be addressed.


Following the principle of [[defence in depth]], a fully patched and correctly configured browser may not be sufficient to ensure that browser-related security issues cannot occur. For example, a [[rootkit]] can [[keystroke logger|capture keystrokes]] while someone logs into a banking website, or carry out a [[man-in-the-middle]] attack by modifying network traffic to and from a web browser. [[DNS hijacking]] or [[DNS spoofing]] may be used to return false positives for mistyped website names, or to subvert search results for popular search engines. Malware such as [[RSPlug]] simply modifies a system's configuration to point at rogue DNS servers.
Following the principle of [[defence in depth]], a fully patched and correctly configured browser may not be sufficient to ensure that browser-related security issues cannot occur. For example, a [[rootkit]] can [[keystroke logger|capture keystrokes]] while someone logs into a banking website, or carry out a [[man-in-the-middle]] attack by modifying network traffic to and from a web browser. [[DNS hijacking]] or [[DNS spoofing]] may be used to return false positives for mistyped website names, or to subvert search results for popular search engines. Malware such as [[RSPlug]] simply modifies a system's configuration to point at rogue DNS servers.

Revision as of 16:26, 26 July 2017

Browser security is the application of Internet security to web browsers in order to protect networked data and computer systems from breaches of privacy or malware. Security exploits of browsers often use JavaScript — sometimes with cross-site scripting (XSS)[1] — sometimes with a secondary payload using Adobe Flash.[2] Security exploits can also take advantage of vulnerabilities (security holes) that are commonly exploited in all browsers (including Mozilla Firefox,[3] Google Chrome,[4] Opera,[5] Microsoft Internet Explorer,[6] and Safari[7]).

Security

Web browsers can be breached in one or more of the following ways:

  • Operating system is breached and malware is reading/modifying the browser memory space in privilege mode [8]
  • Operating system has a malware running as a background process, which is reading/modifying the browser memory space in privileged mode
  • Main browser executable can be hacked
  • Browser components may be hacked
  • Browser plugins can be hacked
  • Browser network communications could be intercepted outside the machine [9]

The browser may not be aware of any of the breaches above and may show user a safe connection is made.

Whenever a browser communicates with a website, the website, as part of that communication, collects some information about the browser (in order to process the formatting of the page to be delivered, if nothing else).[10] If malicious code has been inserted into the website's content, or in a worst-case scenario, if that website has been specifically designed to host malicious code, then vulnerabilities specific to a particular browser can allow this malicious code to run processes within the browser application in unintended ways (and remember, one of the bits of information that a website collects from a browser communication is the browser's identity- allowing specific vulnerabilities to be exploited).[11] Once an attacker is able to run processes on the visitor's machine, then exploiting known security vulnerabilities can allow the attacker to gain privileged access (if the browser isn't already running with privileged access) to the "infected" system in order to perform an even greater variety of malicious processes and activities on the machine or even the victim's whole network.[12]

Breaches of web browser security are usually for the purpose of bypassing protections to display pop-up advertising[13] collecting personally identifiable information (PII) for either Internet marketing or identity theft, website tracking or web analytics about a user against their will using tools such as web bugs, Clickjacking, Likejacking (where Facebook's like button is targeted),[14][15][16][17] HTTP cookies, zombie cookies or Flash cookies (Local Shared Objects or LSOs);[2] installing adware, viruses, spyware such as Trojan horses (to gain access to users' personal computers via cracking) or other malware including online banking theft using man-in-the-browser attacks.

Vulnerabilities in the web browser software itself can be minimized by keeping browser software updated,[18] but will not be sufficient if the underlying operating system is compromised, for example, by a rootkit.[19] Some subcomponents of browsers such as scripting, add-ons, and cookies[20][21][22] are particularly vulnerable ("the confused deputy problem") and also need to be addressed.

Following the principle of defence in depth, a fully patched and correctly configured browser may not be sufficient to ensure that browser-related security issues cannot occur. For example, a rootkit can capture keystrokes while someone logs into a banking website, or carry out a man-in-the-middle attack by modifying network traffic to and from a web browser. DNS hijacking or DNS spoofing may be used to return false positives for mistyped website names, or to subvert search results for popular search engines. Malware such as RSPlug simply modifies a system's configuration to point at rogue DNS servers.

Browsers can use more secure methods of network communication to help prevent some of these attacks:

Perimeter defenses, typically through firewalls and the use of filtering proxy servers that block malicious websites and perform antivirus scans of any file downloads, are commonly implemented as a best practice in large organizations to block malicious network traffic before it reaches a browser.

The topic of browser security has grown to the point of spawning the creation of entire organizations, such as The Browser Exploitation Framework Project,[23] creating platforms to collect tools to breach browser security, ostensibly in order to test browsers and network systems for vulnerabilities.

Plugins and extensions

Although not part of the browser per se, browser plugins and extensions extend the attack surface, exposing vulnerabilities in Adobe Flash Player, Adobe (Acrobat) Reader, Java plugin, and ActiveX that are commonly exploited. Malware may also be implemented as a browser extension, such as a browser helper object in the case of Internet Explorer.[24] Browsers like Google Chrome and Mozilla Firefox can block—or warn users of—insecure plugins.

Flash

Main article: Local shared object § Privacy concerns

An August 2009 study by the Social Science Research Network found that 50% of websites using Flash were also employing flash cookies, yet privacy policies rarely disclosed them, and user controls for privacy preferences were lacking.[25] Most browsers' cache and history delete functions do not affect Flash Player's writing Local Shared Objects to its own cache, and the user community is much less aware of the existence and function of Flash cookies than HTTP cookies.[26] Thus, users having deleted HTTP cookies and purged browser history files and caches may believe that they have purged all tracking data from their computers when in fact Flash browsing history remains. As well as manual removal, the BetterPrivacy addon for Firefox can remove Flash cookies.[2] Adblock Plus can be used to filter out specific threats[13] and Flashblock can be used to give an option before allowing content on otherwise trusted sites.[27]

Charlie Miller recommended "not to install Flash"[28] at the computer security conference CanSecWest. Several other security experts also recommend to either not install Adobe Flash Player or to block it.[29]

Password security model

The contents of a web page are arbitrary and controlled by the entity owning the domain named displayed in the address bar. If HTTPS is used, then encryption is used to secure against attackers with access to the network from changing the page contents en route. For normal password usage on the WWW, when the user is confronted by a dialog asking for their password, they are supposed to look at the address bar to determine whether the domain name in the address bar is the correct place to send the password.[30] For example, for Google's single sign-on system (used on e.g. youtube.com), the user should always check that the address bar says "https://accounts.google.com" before inputting their password.

An un-compromised browser guarantees that the address bar is correct. This guarantee is one reason why browsers will generally display a warning when entering fullscreen mode, on top of where the address bar would normally be, so that a fullscreen website cannot make a fake browser user interface with a fake address bar.[31]

Privacy

Main articles: Internet privacy and Privacy mode

Hardware browser

There have been attempts to market hardware-based browsers running from non-writable, read-only file systems. Data cannot stored on the device and the media cannot be overwritten, presenting a clean executable each time it loads. The first such device was the ZeusGard Secure Hardware Browser, released in late 2013. The ZeusGard website has not been functional since mid-2016 and there does not appear to be any current manufacturer of such devices. Any non-secured web traffic (not using https, for example), could still be subject to man-in-the-middle alteration or other network traffic-based manipulations.

LiveCD

LiveCDs, which run an operating system from a non-writable source, typically come with internet browsers as part of their default image. If the original LiveCD image is free of malware, all of the software used, including the internet browser, will load free of malware every time the LiveCD image is booted.

Browser hardening

Browsing the Internet as a least-privilege user account (i.e. without administrator privileges) limits the ability of a security exploit in a web browser from compromising the whole operating system.[32]

Internet Explorer 4 and later allows the blacklisting[33][34][35] and whitelisting[36][37] of ActiveX controls, add-ons and browser extensions in various ways.

Internet Explorer 7 added "protected mode", a technology that hardens the browser through the application of a security sandboxing feature of Windows Vista called Mandatory Integrity Control.[38] Google Chrome provides a sandbox to limit web page access to the operating system.[39]

Suspected malware sites reported to Google,[40] and confirmed by Google, are flagged as hosting malware in certain browsers.[41]

There are third-party extensions and plugins available to harden even the latest browsers,[42] and some for older browsers and operating systems. Whitelist-based software such as NoScript can block JavaScript and Adobe Flash which is used for most attacks on privacy, allowing users to choose only sites they know are safe - AdBlock Plus also uses whitelist ad filtering rules subscriptions, though both the software itself and the filtering list maintainers have come under controversy for by-default allowing some sites to pass the pre-set filters.[43] The US-CERT recommends to block Flash using NoScript.[44]

Best practice

  • Load clean software: Boot from a known clean OS that has a known clean internet browser
  • Prevent attacks via third-party software: Use a hardened internet browser or add-on-free-browsing mode
  • Prevent DNS manipulation: Use trusted and secure DNS
  • Avoid website-based exploits: Employ link-checking browser plug-ins commonly found in internet security software
  • Avoid malicious content: Employ perimeter defenses and anti-malware software

See also

References

  1. ^ Maone, Giorgio. "NoScript :: Add-ons for Firefox". Mozilla Add-ons. Mozilla Foundation.
  2. ^ a b c NC (Social Science Research Network). "BetterPrivacy :: Add-ons for Firefox". Mozilla Add-ons. Mozilla Foundation. {{cite web}}: |author= has generic name (help); External link in |author= (help)CS1 maint: numeric names: authors list (link)
  3. ^ Keizer, Greg. Firefox 3.5 Vulnerability Confirmed. Retrieved 19 November 2010.
  4. ^ Messmer, Ellen and NetworkWorld. "Google Chrome Tops 'Dirty Dozen' Vulnerable Apps List". Retrieved 19 November 2010.
  5. ^ Skinner, Carrie-Ann. Opera Plugs "Severe" Browser Hole Archived 20 May 2009 at the Wayback Machine. Retrieved 19 November 2010.
  6. ^ Bradly, Tony. "It's Time to Finally Drop Internet Explorer 6" . Retrieved 19 November 2010.
  7. ^ "Browser". Mashable. Retrieved 2 September 2011.
  8. ^ Smith, Dave. "The Yontoo Trojan: New Mac OS X Malware Infects Google Chrome, Firefox And Safari Browsers Via Adware". IBT Media Inc. Retrieved 21 March 2013.
  9. ^ Goodin, Dan. "MySQL.com breach leaves visitors exposed to malware". Retrieved 26 September 2011.
  10. ^ Clinton Wong. "HTTP Transactions". O'Reilly. Archived from the original on 13 June 2013. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  11. ^ "9 Ways to Know Your PC is Infected with Malware".
  12. ^ "Symantec Security Response Whitepapers".
  13. ^ a b Palant, Wladimir. "Adblock Plus :: Add-ons for Firefox". Mozilla Add-ons. Mozilla Foundation.
  14. ^ "Facebook privacy probed over 'like,' invitations". CBC News. 23 September 2010. Retrieved 24 August 2011.
  15. ^ Albanesius, Chloe (19 August 2011). "German Agencies Banned From Using Facebook, 'Like' Button". PC Magazine. Retrieved 24 August 2011.
  16. ^ McCullagh, Declan (2 June 2010). "Facebook 'Like' button draws privacy scrutiny". CNET News. Retrieved 19 December 2011.
  17. ^ Roosendaal, Arnold (30 November 2010). "Facebook Tracks and Traces Everyone: Like This!". SSRN 1717563. {{cite web}}: |access-date= requires |url= (help); Missing or empty |url= (help)
  18. ^ State of Vermont. "Web Browser Attacks". Archived from the original on 13 February 2012. Retrieved 11 April 2012. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  19. ^ "Windows Rootkit Overview" (PDF). Symantec. Retrieved 20 April 2013.
  20. ^ "Cross Site Scripting Attack". Retrieved 20 May 2013.
  21. ^ Lenny Zeltser. "Mitigating Attacks on the Web Browser and Add-Ons". Retrieved 20 May 2013.
  22. ^ Dan Goodin. "Two new attacks on SSL decrypt authentication cookies". Retrieved 20 May 2013.
  23. ^ "beefproject.com".
  24. ^ "How to Create a Rule That Will Block or Log Browser Helper Objects in Symantec Endpoint Protection". Symantec.com. Retrieved 12 April 2012.
  25. ^ "Soltani, Ashkan, Canty, Shannon, Mayo, Quentin, Thomas, Lauren and Hoofnagle, Chris Jay: Flash Cookies and Privacy". 10 August 2009. SSRN 1446862. {{cite web}}: |access-date= requires |url= (help); Missing or empty |url= (help)
  26. ^ "Local Shared Objects -- "Flash Cookies"". Electronic Privacy Information Center. 21 July 2005. Archived from the original on 16 April 2010. Retrieved 8 March 2010. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  27. ^ Chee, Philip. "Flashblock :: Add-ons for Firefox". Mozilla Add-ons. Mozilla Foundation.
  28. ^ "Pwn2Own 2010: interview with Charlie Miller". 1 March 2010. Retrieved 27 March 2010.
  29. ^ "Expert says Adobe Flash policy is risky". 12 November 2009. Retrieved 27 March 2010.
  30. ^ John C. Mitchell. "Browser Security Model" (PDF).
  31. ^ http://feross.org/html5-fullscreen-api-attack/
  32. ^ "Using a Least-Privileged User Account". Microsoft. Retrieved 20 April 2013.
  33. ^ "How to Stop an ActiveX control from running in Internet Explorer". Microsoft. Retrieved 22 November 2014.
  34. ^ "Internet Explorer security zones registry entries for advanced users". Microsoft. Retrieved 22 November 2014.
  35. ^ "Out-of-date ActiveX control blocking". Microsoft. Retrieved 22 November 2014.
  36. ^ "Internet Explorer Add-on Management and Crash Detection". Microsoft. Retrieved 22 November 2014.
  37. ^ "How to Manage Internet Explorer Add-ons in Windows XP Service Pack 2". Microsoft. Retrieved 22 November 2014.
  38. ^ Matthew Conover. "Analysis of the Windows Vista Security Model" (PDF). Symantec Corporation. Retrieved 8 October 2007.
  39. ^ "Browser Security: Lessons from Google Chrome".
  40. ^ "Report malicious software (URL) to Google".
  41. ^ "Google Safe Browsing".
  42. ^ "5 Ways to Secure Your Web Browser". ZoneAlarm.
  43. ^ "Adblock Plus Will Soon Block Fewer Ads — SiliconFilter". Siliconfilter.com. Retrieved 20 April 2013.
  44. ^ "Securing Your Web Browser". Archived from the original on 26 March 2010. Retrieved 27 March 2010. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
Retrieved from "https://en.wikipedia.org/w/index.php?title=Browser_security&oldid=792453758"