[Graham M]

Originally Posted by punky

No its not like that. This tool hasn't found 611 exploits, its found 611 instances that memory isn't checked after an operation. This can lead to a exploit, but only if the surrounding code and function calls allow it. All these defects show that it could be liable to crash, or eat up memory without releasing it until the process is terminated. The guy is scare mongering.

Its no secret Firefox has memory issues, they have tried to be fixed since it was built.

Put it this way, Firefox is open-source. That makes exploit finding extremely easy. Much easier than trial-and-error with IE. The fact that very little has been found, says something. Also, being open-source problems are more likely to be found, and fixed, than being being found and used underground.

Well done Punky, you read my mind