So here's a question.
In the Intego Blog interview, Charlie Miller talks about "dumb fuzzing" - which sounds like he is just sending lots and lots of corrupted PDF files to Preview to find which ones crash the application which is a hint that perhaps that particular corruption is exploitable. That is just a summary.... here is the link.
So my question is.... is this enough information that a bright cookie at Apple could duplicate Miller's technique and find the exploits themselves? If so, what are the rules at pwn2own about how up-to-date a system must be? Could Apple release a security update the night before, and close the exploits that Miller was expecting to use?
At some point Apple has got to think to themselves that having their system fall first for 3 or 4 years in a row is going to cost them enough sales that its worth their while to let someone else get the cream-pie in the face.
And for what its worth, I think OS X is just as safe as it has to be, and not much more. Apple is a business, and they won't spend any more money on security than they have to... but I think they will spend as much as they need to. In other words, at this point there is no profit to be made by spending more money on security. Spend more on security will not bring the rate of malware infections down since the rate is very nearly zero.
Only when the rate of malware infections starts to go up does it make any sense to spend much more on security. I'm sure that malware infections will start to increase in the next few years.... and I'm sure that Apple will start taking security more seriously. Much more seriously. They make a lot of sales based on the perception that Macs are "Safer" (and by "safer" I mean infected less often, I'm not going to get into the Save vs Secure debate).
It would be just like Apple to put out a security update at the last minute to prevent the PR hit. I don't think it will happen, but it would fit their pattern.
legit security researchers will alert a company months before it goes public. they only go public if they get blown off. it's why apple had patches ready last year within days of exploits being shown off. not like they coded the fixes in a few days.