W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2008

[whatwg] The <iframe> element and sandboxing ideas

From: Frode Børli <frode@seria.no>
Date: Wed, 23 Jul 2008 00:22:07 +0200
Message-ID: <31fb000f0807221522s6cc715b0x205bbbba0a99cccf@mail.gmail.com>
The server must escape all user generated content by replacing < with
&lt; etc. This is perfectly secure for all existing browsers. The
sandbox instructs the browser to unescape. Completely fail safe for
all.

On 7/22/08, James Ide <ide at berkeley.edu> wrote:
> I'm not sure that I follow - it seems to me that searching for unescaped
> text and failing is not a reliable solution. As you mention:
>
>> The problem is 1: that the user can easily write </span> in his comment
>> and
>> bypass the sandbox and 2: it is not backward compatible.
>>
>
>  Say I input "</span>" and the application developer has forgotten to
> sanitize user input or permits use of the <span> tag (and has done some poor
> checking for well-formed code). The application may later display a page
> with my input, thus containing (e.g.): <span sandbox=1> </span> </span>,
> where "</span>" in the middle is my input.
>
> Is this a span element with unescaped content ("</span>"), or is it
> malformed HTML? In my eyes, it's the latter and if any UA were to treat it
> this way, it would be trivial to inject more harmful code. On a side note,
> would comments be permitted inside a sandbox? Developers may wish to have
> this functionality, but there is also the concern of a malicious user
> submitting the string "<!--", which, from some brief testing, appears to
> cause problems in IE6 and possibly more UAs. I do not have significant
> experience with parsers so I can't say for sure if these issues are
> showstoppers but they raise some concerns.
>
> If the browser finds unescaped content inside a sandbox it should refuse to
>> display the page - thereby forcing the author to fix this immediately.
>>
>
> As mentioned previously on the topic of sandboxes, such a strict failing
> policy may not be desirable. Perhaps a more gentle approach is only not to
> render the sandbox's contents and perhaps display an error message in its
> stead.
>
> Overall, I'm seeing sandbox elements to be weak safety nets. AFAIK, there is
> no way for a UA alone to perfectly determine what is author- or
> developer-generated and what is user-submitted; user input must go through
> some santizing process to be completely safe.
>
> - James
>

-- 
Sent from Gmail for mobile | mobile.google.com

Best regards / Med vennlig hilsen
Frode B?rli
Seria.no

Mobile:
+47 406 16 637
Company:
+47 216 90 000
Fax:
+47 216 91 000


Think about the environment. Do not print this e-mail unless you really need to.

Tenk milj?. Ikke skriv ut denne e-posten dersom det ikke er n?dvendig.
Received on Tuesday, 22 July 2008 15:22:07 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:03 UTC