Google fixes YouTube xxx spam flaw

Mike Halsey MVP
Jul 5, 2010
Updated • Dec 26, 2012
Google, Youtube
|
1

YouTube owner Google has been forced to act quickly to fix a flaw on it's YouTube video sharing website that allowed hackers to bombard users with pop-up messages, redirecting them to adult websites. The code was placed in the comments section of targeted videos and would run automatically when people watched the clip.

Google says the problem was fixed within only two hours of being reported, according to the BBC.

"We took swift action to fix a cross-site scripting (XSS) vulnerability on youtube.com," a spokesperson said.

"Comments were temporarily hidden by default within an hour, and we released a complete fix for the issue in about two hours.

Hackers had used JavaScript and HTML code to trigger the malicious pop-ups.

"The thing with a cross-site scripting attack is that it will appear that it is a message being posted by that website, which gives it a certain legitimacy, Graham Cluley of security firm Sophos told BBC News.

"It could be used to show a message that tells you to update your password; it could link to a malicious website; or it could attempt to phish you."

For now YouTube is back to it's old self and if you're visiting the site in the next week I thoroughly recommend you click on the football icon during playing videos to add an authentic Vuvuzela soundtrack.

Update: While Google fixed the issue in record time, it needs to be noted that YouTube is still often used by part of its user base to distribute videos that are not allowed on the site. This includes adult movies but also full length movies and other copyrighted materials. Google is usually quick when it comes to deleting those, but sometimes, they slip past to stay on the site for a prolonged period of time (until someone reports them to Google).

Advertisement

Tutorials & Tips


Previous Post: «
Next Post: «

Comments

  1. HNicolai said on July 6, 2010 at 10:07 am
    Reply

    It wasn’t a cross-site scripting (XSS) flaw, it was a html code injection flaw.
    And when I found out of this, then it took at least 3~4 hours before Google made the “Hide comments”-workaround.

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

We love comments and welcome thoughtful and civilized discussion. Rudeness and personal attacks will not be tolerated. Please stay on-topic.
Please note that your comment may not appear immediately after you post it.