On the Content Security Policy Violations due to the Same-Origin Policy
Authors:
Open Access
- 3 April 2017
- conference paper
- Published by Association for Computing Machinery (ACM)
- p. 877-886
Abstract
International audienceModern browsers implement different security policies such as the Content Security Policy (CSP), a mechanism designed to mitigate popular web vulnerabilities, and the Same Origin Policy (SOP), a mechanism that governs interactions between resources of web pages. In this work, we describe how CSP may be violated due to the SOP when a page contains an embedded iframe from the same origin. We analyse 1 million pages from 10,000 top Alexa sites and report that at least 31.1% of current CSP-enabled pages are potentially vulnerable to CSP violations. Further considering real-world situations where those pages are involved in same-origin nested browsing contexts, we found that in at least 23.5% of the cases, CSP violations are possible. During our study, we also identified a divergence among browsers implementations in the enforcement of CSP in sr-cdoc sandboxed iframes, which actually reveals a problem in Gecko-based browsers CSP implementation. To ameliorate the problematic conflicts of the security mechanisms, we discuss measures to avoid CSP violationsKeywords
All Related Versions
This publication has 13 references indexed in Scilit:
- CSPAutoGen2016
- Content Security Problems?2016
- Data Exfiltration in the Face of CSP2016
- Injecting CSP for Fun and Security2016
- May I? - Content Security Policy Endorsement for Browser Extensions2015
- Gradual typing embedded securely in JavaScript2014
- deDacota2013
- PreparedJS: Secure Script-Templates for JavaScript2013
- Reining in the web with content security policy2010
- On the Incoherencies in Web Browser Access Control Policies2010