2015
DOI: 10.1016/j.cose.2014.12.002
|View full text |Cite
|
Sign up to set email alerts
|

SENTINEL: Securing Legacy Firefox Extensions

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
13
0

Year Published

2016
2016
2019
2019

Publication Types

Select...
4
1
1

Relationship

1
5

Authors

Journals

citations
Cited by 16 publications
(13 citation statements)
references
References 17 publications
0
13
0
Order By: Relevance
“…Moreover, the simplified API of the Jetpack framework is not feature-complete and, therefore, various extensions use a mix of the legacy extension development techniques and Addon SDK to access more powerful XPCOM features where necessary. In fact, a recent study [32] shows that in June 2014, only 10.6% of the top 1,000 Firefox extensions were built using the Add-on SDK. We have also performed a similar preliminary experiment to verify those results.…”
Section: A Firefox Extensionsmentioning
confidence: 99%
See 2 more Smart Citations
“…Moreover, the simplified API of the Jetpack framework is not feature-complete and, therefore, various extensions use a mix of the legacy extension development techniques and Addon SDK to access more powerful XPCOM features where necessary. In fact, a recent study [32] shows that in June 2014, only 10.6% of the top 1,000 Firefox extensions were built using the Add-on SDK. We have also performed a similar preliminary experiment to verify those results.…”
Section: A Firefox Extensionsmentioning
confidence: 99%
“…Onarlioglu et al [31] describe Sentinel, a lightweight XPCOM policy enforcer for JavaScript Firefox extensions. An extended version of this work [32] provides a partial and limited defense against extension-reuse attacks by protecting global variables against tampering; however, reuse of globally-exposed sensitive functions (e.g., attacks those described in Section III-C) remain unaddressed. Ter Louw et al [34], [35] present an extension integrity checker and an XPCOM policy enforcement framework built into Firefox.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…We then used a set of extensions (training samples), which are collected from various extension sources (such as Mozilla Add-ons repository, Bugzilla reports [29], other websites that report malicious extensions and related literature) to train the three models. Vulnerable and malicious extension samples are specifically difficult to find (also noted elsewhere [26,27]). Hence, we defined rules and applied them to generate additional training samples such that the detection would be more accurate and efficient.…”
Section: Introductionmentioning
confidence: 99%
“…Barua et al [26] presented an approach to differentiate between legitimate and malicious JavaScript code supplied through unsanitized user inputs to Firefox extensions using a code randomization and point-to analysis techniques. A recent work that allows Firefox users to specify policies for extensions and offers run time enforcement of those policies is discussed in [27]. A user could specify that extensions are allowed to read from the file system and password manager but not allowed to write to either.…”
Section: Introductionmentioning
confidence: 99%