4 ms·
So a vulnerability of this kind would not only affect Firefox but also Chrome and others?
by secmax 10y ago
So a vulnerability of this kind would not only affect Firefox but also Chrome and others?
- nathancahill 10y agoEvery browsers addon runtime is different. Firefox is working on standardizing things with it's Web Extensions API (modeled after Chromium's API). But potentially, yes.
- AgentME 10y agoMost likely. Angular evals stuff from the DOM. Chrome extensions share the DOM with the webpage like Firefox extensions.
- codedokode 10y agoIn Chrome content scripts (the ones that are injected into a page from an extension) run in some kind of isolated mode: https://developer.chrome.com/extensions/content_scripts https://developer.chrome.com/extensions/content_scripts Yet they have some privileges a normal script doesn't have, for example the ability to post messages to parent extension which can be exploited.
- AgentME 10y agoThey still see the same content in the DOM. The extension just has a separate javascript-wrapper around the DOM. This means that an extension will not be affected if a webpage monkey-patches a DOM method to do something else. But if a webpage places some specific text content inside an HTML element, then the extension will see that same text content! (And Angular running in the extension can still choose to recognize that content as a template and eval it.)
- the_duke 10y agoChromes extension APIs do not provide the level of access that Firefox APIs do.
- bzbarsky 10y agoThe topic of discussion here is Firefox webextensions, which are meant to be API-compatible with Chrome extensions and have the same security model.