News for hackers. Stuff that matters.
Re:CNN, NYTimes, Mashable all vulnerable to XSS by msmith on Thursday October 20, 2011 @06:48PM (#3137463)
It's interesting that someone went out of their way to obfuscate the interim.html script:

    document.write('<s'+'cript language="JavaScript" src="');
I guess they were intentionally trying to evade some tool that looks for '<script'?
Re:CNN, NYTimes, Mashable all vulnerable to XSS by jeltz on Thursday October 20, 2011 @06:50PM (#3137471)
My theory is just overzealous protection against having the </script> end tag break that JavaScript block early. Escaping the end tag is necessary.

  document.write(adUrl+'"></s'+'cript>');
Re:CNN, NYTimes, Mashable all vulnerable to XSS by xentronium on Friday October 21, 2011 @01:20AM (#3138550)
http://stackoverflow.com/questions/236073/why-split-the-scri...

Found a stack overflow question with explanation. Again, I believe, only IE couldn't handle word script in the literal string.

Re:CNN, NYTimes, Mashable all vulnerable to XSS by msmith on Friday October 21, 2011 @12:24PM (#3140483)
Ah, I see. Thanks for the pointer.
Re:CNN, NYTimes, Mashable all vulnerable to XSS by lftl on Thursday October 20, 2011 @09:49PM (#3137969)
It's been awhile since I played with it, but I believe there's a legitimate reason for breaking the <script. Possibly one of the older browsers had a broken parser that would interpret that as the beginning of a new script tag?
Re:CNN, NYTimes, Mashable all vulnerable to XSS by xentronium on Friday October 21, 2011 @01:14AM (#3138531)
I believe, it's some sort of IE hack.