IETF Logo Mail Archive

Re: [websec] X-Frame-Options EBNF bug at Mozilla

Julian Reschke <julian.reschke@gmx.de> Wed, 13 February 2013 10:00 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: websec@ietfa.amsl.com
Delivered-To: websec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B48A521F8869 for <websec@ietfa.amsl.com>; Wed, 13 Feb 2013 02:00:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.645
X-Spam-Level:
X-Spam-Status: No, score=-104.645 tagged_above=-999 required=5 tests=[AWL=-2.845, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TyHWg1cn5uam for <websec@ietfa.amsl.com>; Wed, 13 Feb 2013 02:00:16 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id 75FBA21F886A for <websec@ietf.org>; Wed, 13 Feb 2013 02:00:13 -0800 (PST)
Received: from mailout-de.gmx.net ([10.1.76.28]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MARzI-1UBajY3Fne-00BfWM for <websec@ietf.org>; Wed, 13 Feb 2013 11:00:10 +0100
Received: (qmail invoked by alias); 13 Feb 2013 10:00:10 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.102]) [217.91.35.233] by mail.gmx.net (mp028) with SMTP; 13 Feb 2013 11:00:10 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19ytaM6kdFyBT7Em/kTjbuM2q4zDbdtSXq/coPme2 +gMKOdENXnQaEK
Message-ID: <511B6429.7000702@gmx.de>
Date: Wed, 13 Feb 2013 11:00:09 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "Hill, Brad" <bhill@paypal-inc.com>
References: <370C9BEB4DD6154FA963E2F79ADC6F2E279156B0@DEN-EXDDA-S12.corp.ebay.com>
In-Reply-To: <370C9BEB4DD6154FA963E2F79ADC6F2E279156B0@DEN-EXDDA-S12.corp.ebay.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: IETF WebSec WG <websec@ietf.org>
Subject: Re: [websec] X-Frame-Options EBNF bug at Mozilla
X-BeenThere: websec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Web Application Security Minus Authentication and Transport <websec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/websec>, <mailto:websec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/websec>
List-Post: <mailto:websec@ietf.org>
List-Help: <mailto:websec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/websec>, <mailto:websec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Feb 2013 10:00:19 -0000

On 2013-02-11 23:09, Hill, Brad wrote:
> This bug at Mozilla was recently brought to my attention:
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=836132
>
> It seems to indicate that the specified EBNF of using a colon between "ALLOW-FROM" and the URI is not the actual behavior of most user agents that implement that functionality.
>
> Perhaps we should update this to reflect the predominant implementation in the field. (Internet Explorer's)
>
> -Brad

Removing the colon (*not* making it optional) would also be consistent 
with the description in 
<http://blogs.msdn.com/b/ieinternals/archive/2010/03/30/combating-clickjacking-with-x-frame-options.aspx>.

Note that the ABNF needs to be updated to RFC 5234 syntax anyway, and 
that it should only describe the header field value, such as:

X-Frame-Options = "DENY"
                 / "SAMEORIGIN"
                 / ("ALLOW-FROM" RWS URI)

RWS = <RWS, as defined by HTTPbis, P1>
URI = <URI, as defined in RFC3986, Section 3>

(we may want to discuss restricting URI to scheme + authority, though).

Best regards, Julian

v2.23.0 | Report a Bug | By Email