<story><title>MySQL.com compromised via (guess what?) SQL injection</title><url>http://blog.sucuri.net/2011/03/mysql-com-compromised.html</url></story><parent_chain></parent_chain><comment><author>jedsmith</author><text>Actual information with more details, minus zero-content blog:&lt;p&gt;&lt;a href=&quot;http://seclists.org/fulldisclosure/2011/Mar/309?utm_source=twitterfeed&amp;#38;utm_medium=twitter&quot; rel=&quot;nofollow&quot;&gt;http://seclists.org/fulldisclosure/2011/Mar/309?utm_source=t...&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;http://pastebin.com/BayvYdcP&quot; rel=&quot;nofollow&quot;&gt;http://pastebin.com/BayvYdcP&lt;/a&gt;</text></comment>
<story><title>MySQL.com compromised via (guess what?) SQL injection</title><url>http://blog.sucuri.net/2011/03/mysql-com-compromised.html</url></story><parent_chain></parent_chain><comment><author>fmavituna</author><text>Same guys hit Sun.com via SQL Injection as well - &lt;a href=&quot;http://tinkode27.baywords.com/sun-com-sun-mycrosystems-vulnerable-sql-injection/&quot; rel=&quot;nofollow&quot;&gt;http://tinkode27.baywords.com/sun-com-sun-mycrosystems-vulne...&lt;/a&gt;&lt;p&gt;&lt;i&gt;Shameless self plug:&lt;/i&gt; Netsparker ( My startup: &lt;a href=&quot;http://www.netsparker.com/&quot; rel=&quot;nofollow&quot;&gt;http://www.netsparker.com/&lt;/a&gt; ) could have identified both of these vulnerabilities.</text></comment>