2008
DOI: 10.1007/978-3-540-89330-1_23
|View full text |Cite
|
Sign up to set email alerts
|

JavaScript Instrumentation in Practice

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
5

Citation Types

0
29
0

Year Published

2008
2008
2017
2017

Publication Types

Select...
5
2
2

Relationship

0
9

Authors

Journals

citations
Cited by 21 publications
(29 citation statements)
references
References 9 publications
0
29
0
Order By: Relevance
“…However, this will likely make it hard to use dynamic third-party content. Finally, Yu et al [32] present a formal semantics of the interaction between JavaScript and browsers and builds on it a proxy-based rewriting framework for dynamically enforcing automata-based security policies [17]. These policies are quite different from information flow in that they require sparser instrumentation, and cannot enforce fine-grained isolation.…”
Section: Related Workmentioning
confidence: 99%
“…However, this will likely make it hard to use dynamic third-party content. Finally, Yu et al [32] present a formal semantics of the interaction between JavaScript and browsers and builds on it a proxy-based rewriting framework for dynamically enforcing automata-based security policies [17]. These policies are quite different from information flow in that they require sparser instrumentation, and cannot enforce fine-grained isolation.…”
Section: Related Workmentioning
confidence: 99%
“…Many recent works have transformed untrusted JS code to interpose runtime policy enforcement checks [1], [2], [8], [35], [48], [49]. These works cover many diverse attack vectors by which thirdparty content may subvert the checks.…”
Section: Related Workmentioning
confidence: 99%
“…Yu et al [44] and Kikuchi et al [24] present an instrumentation approach for JavaScript in the browser. Their framework allows instrumented code to encode edit automata-based policies.…”
Section: Related Workmentioning
confidence: 99%