4 Replies Latest reply on Oct 4, 2011 12:43 PM by exbrit

    Firefox blocking McAfee ScriptScan

      I have Firefox 4.0.1 & MacAfee SecurityCenter 11.0 running under 64-bit Win 7 Professional SP1.

       

      For the past few weeks Firefox has been occasionally crashing for an unknown reason. About 15 minutes ago I received a Firefox warning that McAfee ScriptScan for Firefox 14.4.0 was known to cause stability problems and advised blocking it, which I have done. Firefox have added ScriptScan to its blocked add-ons list, dated 3 October 2011.

       

      Link: https://addons.mozilla.org/en-US/firefox/blocked/i42

       

      Message was edited by: Plotinus on 10/4/11 5:28:01 AM CDT

       

      Message was edited by: Plotinus on 10/4/11 5:28:39 AM CDT
        • 1. Re: Firefox blocking McAfee ScriptScan
          exbrit

          Thanks for reporting this.  It is a known issue and is being worked on.  I moved this thread to the ViruScan section where you will see several similar threads.

          • 2. Re: Firefox blocking McAfee ScriptScan

            It may or may not be relevant, but I use the Firefox script-blocking Add-on, NoScript.

            • 3. Re: Firefox blocking McAfee ScriptScan
              exbrit

              Plotinus wrote:

               

              It may or may not be relevant, but I use the Firefox script-blocking Add-on, NoScript.

              That's an interesting thought but I don't use that extension so it appears to be happening anyway independently of any other extension or plugin.   I think that extension, if my memory serves me right and without looking it up, was something about blocking Javascript or something like that?

               

              This scriptscan issue has been reported now for a couple of weeks by various people and I have alerted my sources at McAfee about it.

              • 4. Re: Firefox blocking McAfee ScriptScan
                exbrit

                Just got this from McAfee...

                 

                I’ve asked Support to push an FAQ out ASAP, but meanwhile:

                 

                 

                1)    It’s NOT a security issue

                 

                2)    It’s a decision made by Mozilla based on crashes that have been reported to Mozilla

                 

                3)    McAfee is aware of it, has a bug filed and is working with Mozilla to address the problem

                 

                4)    Until it is fixed, the primary workaround is to re-enable the ScriptScanner.  Alternatives include use another browser for now (with most browsers you can import bookmarks and homepages).  Also, SiteAdvisor 3.4 will provide *some* overlapping protection, specifically for scripts run in iFrames on webpages