9225 2010-03-11 09:28:48 +0000 lax interpretation of legacy encoding decl allows attackers to change encoding of a page 2010-10-04 14:00:07 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC All CLOSED FIXED security P3 normal --- 1 zcorpan ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 32902 0 zcorpan 2010-03-11 09:28:48 +0000 The spec says to look at content='' on each meta and try to interpret it as an encoding decl, even if it doesn't have http-equiv=content-type. This allows attackers to change the encoding if a page allows text to be inserted in a <meta name=description content='...'> (or keywords, author, etc). This can cause scripts to execute twice or change the meaning of URLs and form submission. Maybe we should require http-equiv=content-type (possibly also other combinations if compat requires e.g. name=content-type or http-equiv=contenttype). Discussion at http://krijnhoetmer.nl/irc-logs/whatwg/20100311#l-184 34763 1 contributor 2010-04-12 06:43:56 +0000 Checked in as WHATWG revision r4993. Check-in comment: Change how character encodings are sniffed to require an http-equiv attribute, and to only process one character encoding per <meta> element, even if attributes are duplicated. http://html5.org/tools/web-apps-tracker?from=4992&to=4993 34764 2 contributor 2010-04-12 06:47:43 +0000 Checked in as WHATWG revision r4994. Check-in comment: Change how <meta> is processed during parsing to require an explicit http-equiv=content-type where applicable. http://html5.org/tools/web-apps-tracker?from=4993&to=4994 34765 3 ian 2010-04-12 06:49:09 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diffs given above Rationale: Concurred with reporter's comments. 34770 4 zcorpan 2010-04-12 07:29:56 +0000 I haven't done a compat study for this yet. But new bugs can be filed if the algorithm needs tweaking.