News for hackers. Stuff that matters.
Re:Google's XSS game by xss-game-bot on Thursday May 29, 2014 @10:57AM (#7816520)
Hey, thanks - it's a valid concern, though an important point (which isn't really well explained in the document) is that this payload will work even if the tag isn't properly terminated.

One of the reasons for using such broken payloads is to demonstrate that browsers will happily parse broken markup and that approaches such as removing "<.*>" won't be effective as a technique to prevent XSS (because such a regexp won't match an unterminated tag like the example you pointed out).

Still, it could at least use a better explanation. The documentation fairy will take a look!

Re:Google's XSS game by michaelx386 on Thursday May 29, 2014 @02:04PM (#7817643)
Thank you for this explanation. It makes sense to me now as before I would have expected the "<.*>" approach to make it safe. It's a shame browsers are so resilient :)