2011 IEEE Symposium on Security and Privacy 2011
DOI: 10.1109/sp.2011.36
|View full text |Cite
|
Sign up to set email alerts
|

Verified Security for Browser Extensions

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
65
0
1

Year Published

2013
2013
2020
2020

Publication Types

Select...
8
1

Relationship

0
9

Authors

Journals

citations
Cited by 86 publications
(66 citation statements)
references
References 12 publications
0
65
0
1
Order By: Relevance
“…IBEX proposed writing extensions in a high-level language (FINE) that can later by analyzed to ensure conformance with specific policies [21]. In contrast, our work does not require significant changes to web applications.…”
Section: Related Workmentioning
confidence: 99%
“…IBEX proposed writing extensions in a high-level language (FINE) that can later by analyzed to ensure conformance with specific policies [21]. In contrast, our work does not require significant changes to web applications.…”
Section: Related Workmentioning
confidence: 99%
“…Similarly, Dhawan and Ganapathy [6] propose SABRE, a framework for dynamically tracking in-browser information flows to detect when a JavaScript extension attempts to compromise browser security. Guha et al [11] propose IBEX, a framework for extension authors to develop extensions with verifiable access control policies, and for curators to detect policy-violating extensions through static analysis. Wang et al [26] dynamically track and examine the behavior of Firefox extensions using an instrumented browser and a test web site.…”
Section: Related Workmentioning
confidence: 99%
“…IBEX Guha et al [14] develop Fine, a secure-by-construction language for writing extensions. Fine is pure, dependently-typed, and bears no resemblance to idiomatic JS.…”
mentioning
confidence: 99%