W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2012

Re: Proposal: Security checks after same-origin revocation with document.domain

From: Ian Hickson <ian@hixie.ch>
Date: Fri, 22 Jun 2012 23:07:05 +0000 (UTC)
To: Boris Zbarsky <bzbarsky@MIT.EDU>
cc: Bobby Holley <bobbyholley@gmail.com>, public-script-coord@w3.org, w3c@adambarth.com, Johnny Stenback <jst@mozilla.com>, Blake Kaplan <mrbkap@mozilla.com>, Daniel Veditz <dveditz@mozilla.com>
Message-ID: <Pine.LNX.4.64.1206222258530.30734@ps20323.dreamhostps.com>
On Fri, 13 Apr 2012, Boris Zbarsky wrote:
> On 4/13/12 6:38 PM, Ian Hickson wrote:
> > > Actually, having revocation is very important in some scenarios; 
> > > otherwise you can't use document.domain securely at all.
> > 
> > Can you elaborate on that?
> For example, if you have pages A and B at foo.example.com, and a page C 
> at bar.example.com, and A has any sort of way to get to B, and then both 
> A and C set document.domain to "example.com", then not revoking A's 
> access to B gives C access to B.  But B didn't opt in via setting 
> document.domain and may not be expecting access from C.
> As the spec is written right now, you can do this safely as long as A 
> (and that includes all libraries loaded by A and all browser extensions 
> that might interact with both B and A) is very careful to never hold 
> references to any objects from B except the Window and Document.
> If A screws this up (or if a browser extesion screws it up by injecting 
> a B object somewhere into A), it screws B over.

There's lots of other ways to screw it up, e.g. anything on 
foo.example.com that reflects HTML back, even if it checks the origin of 
the submitter, would end up letting B run code in A's origin, letting C do 
whatever it wants with B. Similarly, anything on any other port on any 
other subdomain of example.com can now access A and B. In general, authors 
should IMHO assume that if they've set document.domain to let another 
origin's pages access them, they've given access to the entire origin. If 
that's not acceptable, then they shouldn't use document.domain, but should 
instead use one of the more secure mechanisms like postMessage().

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 22 June 2012 23:07:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:06 UTC