I was thinking about alternative ways of exploiting the browser without going through the process of finding overflows or other common vulnerabilities. The first most obvious thing I come across is exploiting the user space plugins. There are many reasons why attackers might go for this type of targets, one of which is that plugins are not written with security in mind.

Let’s have a look on Firefox extensions security implications. Because extensions make use of standard technologies such as JavaScript, XML, RDF, CSS, it could be possible to transfer malicious code from a remote page into the browser context. Here is a simple scenario:

  1. the user visits evil.com
  2. the malicious site detects the currently installed Firefox plugins
  3. upon detection complete a vulnerable plugin is targeted
  4. based on the plugin type and version, a malicious content is written inside the current document
  5. this content is read by the vulnerable plugin
  6. because the plugin does not perform any data sensitizations, the malicious JavaScript code jumps from the restricted sandbox into the browser context, which is unrestricted.

The result of this kind of attack is quite obvious. Once restricted web script cross into your browser context, higher access permissions are granted. From this point on, the script can install other scripts and modify your file system. Attackers will be able to hijack your browser and backdoor every page you visit using greasemonkey script for example. This means that every page you visit will leak sensitive information about you. It is also worth mentioning that once your browser is compromised the attacker can use it as part of a botnet to attack other machines.