Back in 2006, when worries about click fraud seemed as if they might cause a loss in confidence in Google's search ads, the company argued convincingly that claims of rampant click fraud were based on bad statistics.
On Monday, Google struck again, challenging the accuracy of an IBM X-Force security report issued last week and the security industry's lack of transparency in how it compiles its vulnerability reports.
Conceding that there's some value in bug reports and catalogs of vulnerabilities compiled by security companies and organizations, Adam Mein of Google's security team nonetheless asserts in a blog post that much of the data in these reports is to some extent inaccurate or outdated.
Mein singles out IBM X-Force's 2010 Mid-Year Trend and Risk Report as an example for claiming that 33% of critical and high-risk bugs found in Google services during the first half of 2010 were left unpatched.
"We questioned a number of surprising findings concerning Google’s vulnerability rate and response record, and after discussions with IBM, we discovered a number of errors that had important implications for the report’s conclusions," he wrote. "IBM worked together with us and promptly issued a correction to address the inaccuracies."
It turns out that the 33% figure was based on the belief that one of the supposedly three vulnerabilities affecting Google during the first half of 2010 remained unpatched. In fact, as Mein explains, that one item was mistakenly assumed to be a security flaw due to some confusion about the terminology used to describe it.
The issue was thought to be a stack buffer overflow (a real security risk) when it was actually a stack overflow or stack exhaustion (not in most cases a security risk). So Google actually faced two security vulnerabilities during the first half of 2010 and patched them both.
IBM's correction shows that Google did better than any of the other vendors listed in terms of promptly addressing critical security flaws.
Which company did the worst? IBM.