Is this still a problem with Nod32?

[jayt]

This discussion is in a recent posting in CNET forums concerning the buffer-overflow problem of many AV programs.

TalkBack 6 of 26: Wrong, you didn't read far enough
Post by: dgc49 on 12/12/05

According to Secunia Database at
http://secunia.com/product/1066/

Currently, 0 out of 2 Secunia advisories, are marked as "Unpatched" in the Secunia database.

This applies to the Windows version of NOD32.

[Elwood]

"0 out of 2...are marked as unpatched", this means they are patched, I think...

[Brian N]

Was patched long time ago.

[alglove]

Do you have a link to the CNET discussion?

[jayt]

Nope this post refers to this reply:

TalkBack TalkBack 4 of 27: NOD32
Post by: BTJustice on 12/12/05

I take it NOD32 was just fine.

{QUOTE-> TalkBack 23 of 27: Wrong, you didn't read far enough
Post by: dgc49 on 12/12/05
According to Secunia Database at
http://secunia.com/product/1066/

Currently, 0 out of 2 Secunia advisories, are marked as "Unpatched" in the Secunia database.

This applies to the Windows version of NOD32. <-QUOTE}

This is the link:
http://reviews.cnet.com/4520-3513_7-6400797-1.html?tag=nl.e757

[alglove]

Thanks for the link! :)

dgc49 was pointing out that mrobinson52's "Not according to Secunia" post is a misinterpretation. "0 out of 2 unpatched" means that Eset has patched the flaws. Scroll down the Secunia page, and you will see the pie graph that shows 100% of the vulnerabilities (2 of 2) have been fixed by "vendor patches".

In other words, Secunia says that an updated version of NOD32 is clear... as far as we know! ;)

[jayt]

Thanks alglove. That's the way I read it also. :)