Mozilla patches 'critical' Firefox memory corruption crashes
Summary: Mozilla has released a new version of its flagship Firefox browser with fixes for five security vulnerabilities, one carrying a "critical" rating.
Mozilla has released a new version of its flagship Firefox browser with fixes for five six security vulnerabilities, one carrying a "critical" rating.
The most serious issue addressed in today's Firefox 2.0.0.4 update pertains to browser crashes with evidence of memory corruption. This fix (MFSA 2007-12) rolls up several bug fixes that, under certain conditions, could presumably lead to code execution attacks.
The update also fixes a high-risk cross-site scripting flaw, an XUL pop-up spoofing bug, a vulnerability that could allow path abuse in cookies, a hole in APOP authentication and a persistent auto-complete denial-of-service flaw.
So far this year, Mozilla has issued shipped fixes for 17 Firefox security issues.
As expected, Mozilla also shipped the final Firefox 1.5 version with patches for the flaws discussed above. This version of Firefox 1.5 includes an auto-update mechanism to migrate users to the more secure/stable Firefox 2 versions.
Firefox 1.5.0.12 is available for download here but all users are encouraged to upgrade to Firefox 2.
Over the coming weeks, Mozilla will be presenting 1.5.0.12 users with a notification message that will offer users a "major update" to Firefox 2. Upon confirmation, a user’s browser will be upgraded from 1.5.0.12 to 2.0.0.4, according to a post on the Mozilla Developer blog.
Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.
Talkback
Huh?
Me neither
I have
I've never had it happen
I really think . . .
On PCLinuxOS 2007, FF will occasionally just quit on it's own, but I think that's due to me running it off the Live CD . . .
Once and for all ...
The problem described is a Firefox problem. That is why it is a Firefox patch. You don't have to look any further then that!
Excellent point - for the most part.
Right on the money - except, isn't MCE supposed to be more like XP Pro with the media center stuff slapped on?
The only other consideration I can think of why any app would behave differently on various flavors of XP - age and corruption. Maybe one box got hit with spyware or viruses that left some registry crud behind after it was removed. The same can be said of many AV apps - Norton is one of the WORST offenders.
At any rate, as you said, it IS a Firefox issue.
True, I took a short cut.
How many people do that?
I'm glad they fix the memory error however, they have a history of being a route to attackers into your system.
My systems
I don't believe they are questioning leaving the ....
I have too
Second the motion !
Henri
Only if you apply this new patch ....
It must not be a problem if you haven't seen it!
So are you trying
How is that relevant?
I've got You Beat!
<br>
I've had several crashes
Still, I'd never go back to IE.
Thanks for the heads up, Ryan