1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Buggy McAfee update slams Windows XP PCs

Discussion in 'Security and Privacy' started by broni, 2010/04/21.

  1. 2010/04/21
    broni

    broni Moderator Malware Analyst Thread Starter

    Joined:
    2002/08/01
    Messages:
    21,701
    Likes Received:
    116
    http://isc.sans.org/diary.html?storyid=8656

    McAfee's "DAT" file version 5958 is causing widespread problems with Windows XP SP3. The affected systems will enter a reboot loop and loose all network access. We have individual reports of other versions of Windows being affected as well. However, only particular configurations of these versions appear affected. The bad DAT file may infect individual workstations as well as workstations connected to a domain. The use of "ePolicyOrchestrator ", which is used to update virus definitions across a network, appears to have lead to a faster spread of the bad DAT file. The ePolicyOrchestrator is used to update "DAT" files throughout enterprises. It can not be used to undo this bad signature because affected system will lose network connectivity.

    The problem is a false positive which identifies a regular Windows binary, "svchost.exe ", as "W32/Wecorl.a ", a virus. If you are affected, you will see a message like:

    The file C:WINDOWSsystem32svchost.exe contains the W32/Wecorl.a Virus.
    Undetermined clean error, OAS denied access and continued.
    Detected using Scan engine version 5400.1158 DAT version 5958.0000.

    McAfee released an updated DAT file, and an "EXTRA.DAT" file to fix the problem. An EXTRA.DAT file is a patch to just fix the bad signature. McAfee's support web sites currently respond slowly and are down at times, likely due to the increased load caused by this issue.

    Several readers reported that this procedure worked to recover:

    1 - Boot the system in "Safe Mode "
    2 - copy extra.dat in c:/program files/common files/mcafee/engine
    3 - reboot.

    If you lost "svchost.exe ", then you need to copy it back to c:/Windows/system32/svchost.exe while in safe mode. This fix has to be applied locally at the workstation. However, it may be possible to do this remotely if your workstations support Intel's "vPro" technology. We should have a link to instructions shortly.

    Additional information from McAfee: http://community.mcafee.com/thread/24056?tstart=0
    McAfee Knowledgebase Article: https://kc.mcafee.com/corporate/index?page=content&id=KB68780
    EXTRA.DAT file: http://home.mcafee.com/VirusInfo/VirusProfile.aspx?key=265240.
     
  2. 2010/04/27
    Retirednow

    Retirednow Inactive

    Joined:
    2010/04/05
    Messages:
    24
    Likes Received:
    0

  3. to hide this advert.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.