How to fix Critical Vulnerability in Firefox 3.5

Hello there! If you are new here, you might want to subscribe to the RSS feed for updates on this topic.

Few weeks back Firefox had moved to version 3.5.But i found Firefox 3.0.12 version much stabler than Firefox 3.5 as i used to encounter crashes due to bad memory management.In addition to this a bug affects Firefox’s new JavaScript rendering engine(TraceMonkey) and has been termed as highly critical by Secunia.

The security hole has to do with a flaw in the way Firefox 3.5 handles Javascript,a powerful programming language heavily used on popular Web sites. Specifically, the vulnerability was introduced with the addition of the Tracemonkey, a new feature in 3.5 that is designed to dramatically speed up the rendering of Javascript.Hackers can gain control of any user’s system by installing spy wares when they visit an harmful website.Mozilla had said they are working on a fix asap.

Temporary solution would be to disable the Trace monkey engine.
Next in the address bar type “about:config” without quotes.
In the box type “jit”. and search for this “javascript.options.jit.content”.
Change its value from True to False.

What changes you observe

Slower speed as it gets reverted back to older rendering engine and its not that bad either or use Noscript

If you feel that’s a pain then download the Firefox 3.5.1 version which fixes the bug but its not released officially yet.Martin from Ghacks has the latest of the Windows version uploaded to a external mirror.You can download Mozilla Firefox 3.5.1

Popularity: 1% [?]

If you enjoyed this post, make sure you subscribe to my RSS feed! Start Slide Show with PicLens Lite