Difference between revisions of "Cross-Origin iFrame"
|Line 20:||Line 20:|
* [https://www.verygoodsecurity.com/blog/posts/iframes-as-a-security-feature Iframes as a Security Feature] does actually acknowledge some of the security problems with iFrames.
* [https://www.verygoodsecurity.com/blog/posts/iframes-as-a-security-feature Iframes as a Security Feature] does actually acknowledge some of the security problems with iFrames .
Revision as of 10:50, 12 March 2021
Full Title or Meme
The Inline Frame, or iFrame was introduced to allow isolated web pages from unrelated entities to embed content seamlessly into a web page.
- Frames and Framesets were introduced early in browser history to enable refreshing only a portion of a web page to improve responsiveness of web pages in the days of low bandwidth data communications.
- Identity features like OpenID Connect and WebAuthn 2 depends on the Cross-Origin iFrame for a seamless User Experience when identity is provided by a different web site than the Relying Party.
- Limitations that have been placed on iFrames can (with the exception of running plugins) be disabled by the source web site which may not fully share the user's security concerns.
- Run plug-ins
- Submit forms - disabled by allow-forms
- Change the parent web page’s URL - disabled by allow-top-navigation
- Read cookies or local storage, even if it’s from the parent domain
- Open new tabs, new windows or pop-up windows - partially disabled by allow-popups
- Access data from Origin URL - allow-same-origin