[ad]<\/p>\n
Ah a bug in our beloved Firefox<\/a>, after the latest 3.5 update (which sees some definite improvements).<\/p>\n The last one I recall was the Clickjacking Vulnerability<\/a>, which also effected Chrome<\/a>.<\/p>\n It seems like it’s not too serious of an issue and will only cause crashing, there’s no room for remote exploitation or code execution. So it may be an annoyance, but if it’s true – it’s not that serious.<\/p>\n Mozilla is denying that a bug that crashes Firefox 3.5 is a security vulnerability, countering earlier reports that the company’s latest browser contained a flaw even though it had just been patched.<\/p>\n In a Sunday post to Mozilla’s security blog, Mike Shaver, the company’s vice president of engineering, said that the bug, which had originally been disclosed on the milw0rm hacker site, is not a vulnerability. “The reports by press and various security agencies have incorrectly indicated that this is an exploitable bug,” Shaver said. “Our analysis indicates that it is not, and we have seen no example of exploitability.”<\/p>\n Exploit code hit milw0rm last Wednesday. Firefox developers immediately logged the bug into Bugzilla, Mozilla’s change- and bug-tracking database. The bug, continued Shaver, does crash Firefox 3.5 — and the recently-released 3.5.1 — in some situations. But there’s no way for an attacker to exploit that by injecting malicious code on the machine. The bug can crash Windows, Mac and Linux editions of Firefox, including Firefox when it’s being run on the still-unfinished Windows 7. <\/p><\/blockquote>\n I guess they will fix it soon enough in the next release (3.5.2) which should come along fairly shortly. I’d have to say I believe the Mozilla developers if they say it’s not exploitable.<\/p>\n So it’s not too big of an issue to worry about, just wait for the next patch roll out and you should be saved from any random crashes caused by malicious sites.<\/p>\n Both Shaver in his blog post and developers on Bugzilla noted that the Firefox crash on Macs was due to a flaw in Apple’s operating system, specifically the ATSUI system library. “We have reported this issue to Apple, but in the event that they do not provide a fix we will look to implement mitigations in Mozilla code,” Shaver said.<\/p>\n Mozilla developer Vladimir Vukicevic countered that it was unlikely Apple would fix the problem. “We’ve reported this and similar bugs in the past to Apple; they have so far had no interest in fixing such bugs in their font rendering subsystems, especially if they’re in ATSUI and not CoreText,” said Vukicevic on Bugzilla.<\/p>\n Another Mozilla hand suggested that the Mac OS X bug may affect other browsers as well. “Chances are more applications use the same buggy API (Safari? Chrome?),” Andreas Gal said. Gal, a project scientist at the University of California-Irvine, was a key contributor to the TraceMonkey JavaScript engine that Mozilla added to Firefox with Version 3.5.<\/p>\n Just last Thursday, Mozilla patched Firefox 3.5 for the first time, issuing a fix for a critical vulnerability in TraceMonkey’s just-in-time (JIT) compiler. In the run-up to creating a fix for that flaw, Mozilla developers speculated that the hacker had dug through Bugzilla to find information that helped him exploit the vulnerability. <\/p><\/blockquote>\n I’ve said for quite a while that open source is a double edged sword, especially when resources such as Bugzilla are public and allow people with malicious intent to dig through the archives and look for bugs that could be exploitable.<\/p>\n With the code being open and the bugs being open too, it makes it much easier to develop exploits.<\/p>\n Thankfully it also leads to less bugs and them being fixed faster, I know which I prefer any day.<\/p>\n You can find the exploit on milw0rm here:<\/p>\n