Simon Willison’s Weblog

Dangers of remote Javascript. Perl.com got hit by a JavaScript porn redirect when the domain of one of their advertisers expired and was bought by a porn company. Nat Torkington suggests keeping track of the expiration dates on any third party domains that are serving JavaScript on your site.

Posted 20th January 2008 at 9:49 am

Tagged domains, javascript, nattorkington, oreilly, perldotcom, security, xss

4 comments

Someone could make a nice service to take care of this. Scrapes some pages from your site, checks the domains of external JS. E-mails you when one is in danger of expiring.

Mark Jaquith - 21st January 2008 05:40 - #
Less critical but the same goes for blog comments, where it seems to be deliberate spammer strategy; switch domains months after making a comment

Harry Fuecks - 21st January 2008 07:53 - #
Serving up other people's JavaScript on your site? Is this O'Reilly's unveiling of the WTF 2.0 concept?

Paul Boddie - 21st January 2008 14:43 - #
Sadly, Paul, this is common practice in ad networks.

Jeremy Dunck - 22nd January 2008 00:44 - #

Comments are closed.