Why did avast! 4 fail in the latest round of vb100 testing?? They say they were testing version 4.1.399 and the latest version out is 4.1.396. There is as problem some where as these version don’t match. Here is the information I got from the following url:
last fail was imho because VBTN couldn’t/wouldn’t manage to switch the avast Shield / on-access-scanner to test “on open” instead of “before execute”(default setting & pretty safe)…
maybe a repetition now…?
see board search, lots of threads on this sad topic
I don’t have the magazine yet… so I don’t really know. But I’ve heard that it’s because avast missed a single sample somewhere (don’t know which/where, though)…
By the way,according to @risk, F-Secure has 2 problems:
Malformed LHA Archive Buffer Overflow and
Content Detection Bypass
Norton has one
Remote Code Execution
I didn’t see anything about avast
-max