Towards Improving Browser Extension Permission Management and User Awareness

Abstract

Browsers have become the de-facto platform for users and their online presence. They have also become a rich environment for 3rd party extensions that enrich the user browsing experience by extending upon the browser's functionalities. Protecting user privacy against malicious or vulnerable extensions is an important task performed by modern browser platforms such as Google Chrome and Safari. To do so, these platforms adopt a per-extension permission model, where each extension is given a set of permissions based on its requirements. These models suffer from coarse-grained access controls and insufficient user awareness. In this paper we implement a runtime framework as a browser extension called REM. REM monitors the accesses made by 3rd party Chrome extensions, informs users of the accesses, and allows them to customize the permissions given to extensions. The custom permission settings are enforced by the framework at runtime. We evaluated our framework on popular Chrome extensions & were successful in monitoring and controlling their accesses with little overhead. We also conducted a user study to evaluate the effectiveness of REM compared to current standard methods.

DOMtegrity: ensuring web page integrity against malicious browser extensions

“…Proposals in this category require users to trust one particular extension and install it consciously. Marouf et al proposed a run-time framework called REM that monitors the access made by extensions and provides customized permission [11]. They developed an extension for monitoring other extension based on REM.…”

“…Existing solutions to prevent malicious extensions generally involve changing the browser's internal design [4], [5], [6], strengthening the vetting process of repositories [2], [7], [8], [9], [10], asking users to install yet another (trusted) extension that detects malicious behaviour of other extensions [11], [12] or requiring an external hardware device (e.g., Cronto) that performs out-of-band transaction verification.…”