HTTP Header X-Frame-Options
draft-ietf-websec-x-frame-options-01

The information below is for an old version of the document
Document Type Active Internet-Draft (websec WG)
Last updated 2012-11-16 (latest revision 2012-10-22)
Replaces draft-gondrom-x-frame-options
Stream IETF
Intended RFC status Informational
Formats pdf htmlized bibtex
Reviews
Stream WG state In WG Last Call
Revised I-D Needed - Issue raised by WGLC
Document shepherd Alexey Melnikov
IESG IESG state AD is watching
Consensus Boilerplate Unknown
Telechat date
Responsible AD Barry Leiba
Send notices to websec-chairs@tools.ietf.org, draft-ietf-websec-x-frame-options@tools.ietf.org, alexey.melnikov@isode.com
WEBSEC                                                           D. Ross
Internet-Draft                                                 Microsoft
Intended status: Informational                                T. Gondrom
Expires: April 26, 2013                                 October 23, 2012

                      HTTP Header X-Frame-Options
                  draft-ietf-websec-x-frame-options-01

Abstract

   To improve the protection of web applications against Clickjacking
   this standard defines an http response header that declares a policy
   communicated from a host to the client browser on whether the browser
   must not display the transmitted content in frames of other web
   pages.  This drafts serves to document the existing use and
   specification of X-Frame-Options.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 26, 2013.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as

Ross & Gondrom           Expires April 26, 2013                 [Page 1]
Internet-Draft               X-Frame-Options                October 2012

   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . . . 3
   2.  X-Frame-Options Header  . . . . . . . . . . . . . . . . . . . . 3
     2.1.  Syntax  . . . . . . . . . . . . . . . . . . . . . . . . . . 3
     2.2.  Backus-Naur Form (BNF)  . . . . . . . . . . . . . . . . . . 4
     2.3.  Design Issues . . . . . . . . . . . . . . . . . . . . . . . 5
       2.3.1.  Enable HTML content from other domains  . . . . . . . . 5
       2.3.2.  Browser Behaviour and Processing  . . . . . . . . . . . 5
     2.4.  Examples of X-Frame-Options Headers . . . . . . . . . . . . 6
       2.4.1.  Example scenario for the ALLOW-FROM parameter . . . . . 6
   3.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 6
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
     4.1.  Registration Template . . . . . . . . . . . . . . . . . . . 7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 7
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 7
     6.1.  Normative References  . . . . . . . . . . . . . . . . . . . 7
     6.2.  Informative References  . . . . . . . . . . . . . . . . . . 7
   Appendix A.  Description of a Clickjacking attack . . . . . . . . . 8
     A.1.  Shop  . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
     A.2.  Confirm Purchase Page . . . . . . . . . . . . . . . . . . . 9
     A.3.  Flash Configuration . . . . . . . . . . . . . . . . . . . . 9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 9

Ross & Gondrom           Expires April 26, 2013                 [Page 2]
Internet-Draft               X-Frame-Options                October 2012

1.  Introduction

   In 2009 and 2010 many browser vendors ([Microsoft-X-Frame-Options],
   [CLICK-DEFENSE-BLOG], [Mozilla-X-Frame-Options]) introduced the use
   of a non-standard http header RFC 2616 [RFC2616] "X-Frame-Options" to
   protect against Clickjacking [Clickjacking].  This draft is to
   document the current use of X-Frame-Options header and shall in the
   future be replaced by the Frame-Options [FRAME-OPTIONS] standard.

   Existing anti-ClickJacking measures, e.g.  Frame-breaking Javascript,
   have weaknesses so that their protection can be circumvented as a
   study [FRAME-BUSTING] demonstrated.

   Short of configuring the browser to disable frames and script
   entirely, which massively impairs browser utility, browser users are
   vulnerable to this type of attack.

   The "X-Frame-Options" allows a secure web page from host B to declare
Show full document text