TinKode reported to us another sql injection vulnerability in one of Yahoo! subdomains.  From what I saw looking at the screenshots provided by him it’s another blind sql injection but, since we don’t test anymore high risk bugs in another systems without the owners consent, I couldn’t say for sure how much damage can do a possible attacker if this vulnerability is exploited.

This is not the first and probably not the last sql injection vulnerability discovered by a romanian pentester in Yahoo! subdomains. Looking back at our articles we can see that Yahoo! is dealing with a big list of vulns, too many for a huge company with billions of members. We are not here to judge them, but this is a fact: Yahoo! needs a full security audit to prevent those things happen so often.

First time it was a big “wooow” for us to find a sql injection vuln in their domains, but now this is too damn usual. It’s like we are talking about Yahoo! xss’s, everybody can have or discover a piece of that, even a 12 year old kid, with an experience of 6 months in “hacking” bussiness. And this is sad. I can handle with xss attacks, I can protect my ass against them, but it’s impossible to mitigate a sql injection from my user side. This is what worries me right now. But enough with this emo speech.

Yahoo! staff was notified and we are waiting to see the vulnerability fixed before the screenshots will be made public on HackersBlog.

Related Posts

• November 13, 2009 -- [Update] SQL Injection in careers.yahoo.com (patched)
• February 23, 2011 -- Concurs fara premii
• August 30, 2010 -- Deface (?!?) pe Cotidianul.ro
• April 21, 2010 -- France2.fr – France4.fr – in asteptarea atacului?
• December 24, 2009 -- Forumul Andreei Balan spart