Sadly however the media are often written by brainless morons (like myself on certain days) and only note that this list shows 'known public issues' the keyword here is public issues, knowing a programs issues is often a good thing as it allows (in the open source world) the developers from various backgrounds to collaborate together towards a fix.
Not to long ago i remember reading a similar report by RedHat which tracked there issues and put them alongside Microsoft's and showed there turn around time for fixes, whom discovered them and there patch/fix status and based on the report it showed RedHat having far more issues, but a very quick turn around basis and most issues being discovered by the RedHat devs themselves.. meaning they we're finding and fixes there own issues which is often the case with Drupal, Joomla! and Wordpress and most other PHP based systems, phpNuke being the exception :P
What does this mean all together ? quite simply really, this report does nothing really for anyone out there other than the media type whom wish to get a story out there or create a little chaos. Mathias of the Joomlatools crew touched on this citing a Belgium Chicken massacre story, to quote:
It reminds me of the Belgian dioxine affair a couple of years back. Some eggs and chickens were discovered to contain the toxic dioxine. The press and the public opinion went insane, there was a huge political crisis, and 7 million chickens were destroyed.
When it finally blew over, it turned out the dose was less than 100mg and no direct threat to public health. And nobody seemed to get that it was actually good news: If the Belgian food inspection can detect such small amounts of toxics, we can be pretty reassured that our food is safe.
Even the likes of Apple are facing stupid titles like 'Apple gets bruised in vulnerability report' has the report gone into any depth of detail other than found issues I'm quite certain we all know which application vendor would be on top (sup bill).
Kris Lamb operations manager for said report is quoted as saying:
"Without a unified process for disclosing vulnerabilities, the research industry runs the risk of actually fueling online criminal activity,"
"There is a reason why X-Force does not publish exploit code for the vulnerabilities we have found, and perhaps it is time for others in our field to reconsider this practice."
While most developers will agree that issues should be shared and known about by all users I'm sure at the same time they are wishing the IBM lot would have actually taken time to place further information into there report such as:
- how quick the issues are fixed
- are they fixed as of current version

