Angular 1.x Banned from Firefox Addons
Many commenters here seem to be completely misunderstanding the situation.<p>Browser extensions are really dangerous; if you need to keep your machine secure, you shouldn&#x27;t use any IMHO. By definition, browser extensions need to be able to access things such as page content. What would stop someone from writing a extension that captures your bank credentials? <i>Nothing.</i><p>Obviously no security-conscious user is going to install a bank credential stealing extension. But what about bugs in extensions? If a buggy extension can be made to execute arbitrary code, it is as dangerous as a malicious extension (if the arbitrary code execution works in the same circumstances).<p>Angular 1.x basically runs eval on DOM content. That&#x27;s how it works, it&#x27;s not a vulnerability in normal use. You make a web page using Angular, and possibly the user has a way to eval arbitrary JS code through Angular, but then they have the developer console so they can run arbitrary code anyway.<p>With browser extensions it&#x27;s different. The extension is from one source and runs with one set of privileges, and the page comes from someone else and has less privileges. Now if anything from the page can be eval&#x27;d in the extension, that&#x27;s privilege escalation. Someone creating a site can run malicious content as a browser extension.<p>It&#x27;s probably possible to sanitize all external inputs used in the browser extension such that privilege escalation isn&#x27;t possible, but the Angular team has tried hard with their sandbox solution with no success. Extension developers will hardly do much better, so it makes sense for Mozilla to ban the whole library.<p>Angular wasn&#x27;t designed for browser extensions.<p>WRT the security researcher and Mozilla not disclosing other known sandbox vulnerabilities, that&#x27;s missing the point (but an interesting discussion in itself).