itteam
July 12th, 2007, 06:14 AM
Hi all
Me and my fellow sysadmins have just spent a few hours chasing what we thought was a zero day virus around our corporate network. We now believe it to be a bug in the latest version of NOD32.
Whenever anyone of our machines that has the current version of NOD32 installed attempts to access any directory that contains JPSoftware's 4NT executables, the machine will either hard reset immediately or get a BSOD. We're not sure which exact file is causing the issue - we've now just excluded AMON from scanning that directory entirely. The version of 4NT is pretty old (v3 or v4) but it also seems to occur on some machines running the latest v8.02.
This only occurs on machines which updated their NOD32 today. If an older version of NOD32 is installed, the machine can browse the folder just fine.
My NOD32 info is below. I've also RAR'd up the Windows minidump info that the crash causes and can mail that if required.
For now we're excluding the directory under AMON and will look to upgrade all users if v8.02 proves to solve the issue (some people with 8.02 have no problems, others do).
Thanks
Andrew
NOD32 antivirus system information
Virus signature database version: 2394 (20070711)
Dated: Wednesday, 11 July 2007
Virus signature database build: 10304
Information on other scanner support parts
Advanced heuristics module version: 1.063 (20070710)
Advanced heuristics module build: 1161
Internet filter version: 1.002 (20040708)
Internet filter build: 1013
Archive support module version: 1.053 (20070524)
Archive support module build version: 1189
Information about installed components
NOD32 For Windows NT/2000/XP/2003/Vista/x64 - Base
Version: 2.70.32
NOD32 For Windows NT/2000/XP/2003/Vista/x64 - Internet support
Version: 2.70.32
NOD32 for Windows NT/2000/XP/2003/Vista/x64 - Standard component
Version: 2.70.32
Operating system information
Platform: Microsoft Windows XP
Version: 5.1.2600 Service Pack 2
Version of common control components: 5.82.2900
RAM: 2047 MB
Processor: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz (2400 MHz)
Me and my fellow sysadmins have just spent a few hours chasing what we thought was a zero day virus around our corporate network. We now believe it to be a bug in the latest version of NOD32.
Whenever anyone of our machines that has the current version of NOD32 installed attempts to access any directory that contains JPSoftware's 4NT executables, the machine will either hard reset immediately or get a BSOD. We're not sure which exact file is causing the issue - we've now just excluded AMON from scanning that directory entirely. The version of 4NT is pretty old (v3 or v4) but it also seems to occur on some machines running the latest v8.02.
This only occurs on machines which updated their NOD32 today. If an older version of NOD32 is installed, the machine can browse the folder just fine.
My NOD32 info is below. I've also RAR'd up the Windows minidump info that the crash causes and can mail that if required.
For now we're excluding the directory under AMON and will look to upgrade all users if v8.02 proves to solve the issue (some people with 8.02 have no problems, others do).
Thanks
Andrew
NOD32 antivirus system information
Virus signature database version: 2394 (20070711)
Dated: Wednesday, 11 July 2007
Virus signature database build: 10304
Information on other scanner support parts
Advanced heuristics module version: 1.063 (20070710)
Advanced heuristics module build: 1161
Internet filter version: 1.002 (20040708)
Internet filter build: 1013
Archive support module version: 1.053 (20070524)
Archive support module build version: 1189
Information about installed components
NOD32 For Windows NT/2000/XP/2003/Vista/x64 - Base
Version: 2.70.32
NOD32 For Windows NT/2000/XP/2003/Vista/x64 - Internet support
Version: 2.70.32
NOD32 for Windows NT/2000/XP/2003/Vista/x64 - Standard component
Version: 2.70.32
Operating system information
Platform: Microsoft Windows XP
Version: 5.1.2600 Service Pack 2
Version of common control components: 5.82.2900
RAM: 2047 MB
Processor: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz (2400 MHz)