@ThomH
Seriously?
I don't want to start a flame war, but I wonder what you consider 'pro-active'.
1) releasing security updates in a timely fashion before the details have been released to the hacker/script-kiddy community (mostly) a-la Apple or
2) waiting 6 months for maximum damage to be done after making a big fanfare announcement about the forthecoming fix (including details of how to implement the exploit) and then finally patching - a-la guesswho
I may be wrong of course, but this certainly seems to be my perception of each companies approach to fixing the bugs that will inevitably occur in any software development cycle.
This one to be honest just seems like a genuine error in checking versions. Not inexcusable but totally understandable in how it happened.