Secunia CSI7
Advisories
Research
Forums
Create Profile
Our Commitment
PSI
PSI API
CSI
OSI
xSI
Vulnerabilities
Programs
Open Discussions
My Threads
Create Thread
Statistics
About

Forum Thread: End of Life for NOD32 v4x

You are currently viewing a forum thread in the Secunia Community Forum. Please note that opinions expressed here are not of Secunia but solely reflect those of the user who wrote it.

This thread was submitted in the following forum:
Programs

Relating to this vendor:
ESET
And, this specific program:
ESET NOD32 Antivirus 4.x

This thread has been marked as locked.
OswaldG End of Life for NOD32 v4x
Member 17th Nov, 2011 17:06
Ranking: 0
Posts: 4
User Since: 17th Aug, 2010
System Score: N/A
Location: N/A
Version 5 has a serous bug that interferes with external USB drives on XP SP3 32-bit. ESET is recommending users roll back to version 4.x as a workaround while the bug is addressed. I find no documentation on ESET's site that version 4 is at end-of-life and no longer supported. All I can find is end of support for version 2.7. Can someone direct me to documentation from ESET that indicates end of support for version 4?

Secunia PSI says "This program was detected as being End-of-Life, which means that the vendor no longer supports this program. It is strongly recommended that you upgrade to a newer version of this program or uninstall it from your PC." but I cannot find anything that suggests that they are no longer supporting 4x installations.

mogs RE: End of Life for NOD32 v4x
Expert Contributor 17th Nov, 2011 18:31
Score: 2265
Posts: 6,266
User Since: 22nd Apr 2009
System Score: 100%
Location: UK
Last edited on 17th Nov, 2011 18:44
@OswaldG

Hello.
The issue has been discussed on the following thread :-
http://secunia.com/community/forum/thread/show/117...

Hope it's of some help.....regards,

--
Was this reply relevant?
+0
-0
OswaldG RE: End of Life for NOD32 v4x
Member 17th Nov, 2011 21:47
Score: 0
Posts: 4
User Since: 17th Aug 2010
System Score: N/A
Location: N/A
Thanks. My post wasn't exactly the same situation. I'm posting about the home version (if I recall from my PSI installation, my PSI isn't licensed for business use anyway), and my question has less to do with telling the difference between one version of 4x and another, but more to do with understanding the exact mechanism under which Secunia labels something as "end of life." Rather than how Secunia can tell between the home version and the business version, it's more about is 4x correctly marked as end-of-life regardless of whether it's home or business.

It's not simply whether a program is the latest version or not, for example. I have versions of other software installed even though there is at least one major version newer available. PSI correctly does not label them as end-of-life. For example does Secunia mark Office 2007 as end of life because 2010 is out? I don't think it does.

ESET did not stop supporting 4x as far as I can tell.
Was this reply relevant?
+0
-0
mogs RE: End of Life for NOD32 v4x
Expert Contributor 17th Nov, 2011 22:14
Score: 2265
Posts: 6,266
User Since: 22nd Apr 2009
System Score: 100%
Location: UK
@OswaldG

I understand what you're "saying".....I merely wished to point you to discussion that had already touched upon the subject.....I'm presuming, that because versions cannot be differentiated, there is difficulty being certain of the security status of either....it may be that is deemed to be not properly supporting the program......but that's all assumption on my part.
Support will hopefully clarify the situation for you in the morning. Sorry I can't be of more help.
Regards,

--
Was this reply relevant?
+0
-0
ve2mrx RE: End of Life for NOD32 v4x
Member 23rd Nov, 2011 22:44
Score: -1
Posts: 22
User Since: 16th Feb 2008
System Score: 99%
Location: Montreal, CA
Hi!
I want to add my voice to this topic. I'm using Eset Antivirus 4.2.71.2 (Business edition) and PSI detects it as End-Of-Life.

This cannot be End-of-life, since there is no replacement available for the business edition! I guess that PSI looks at some file, and flags my Business edition copy as a personal one? Else, if the files are the same, then Eset cannot EOL v4.2.71.2 since it's still good for business users, right?

Anyway, thanks for your support, and I will create an ignore rule for the program in the mean time...

Thanks,
Martin Boissonneault

P.S. I'm using ESET antivirus Business Edition, just not for business computers. Since I manage the family's many computers, I use the remote administration feature in the Business Edition version to watch over them.
Was this reply relevant?
+0
-0
OswaldG RE: End of Life for NOD32 v4x
Member 24th Nov, 2011 15:38
Score: 0
Posts: 4
User Since: 17th Aug 2010
System Score: N/A
Location: N/A
I asked about this on the ESET forum, and they said they would contact Secunia about it. Today, PSI reports ESET 4.2.71.2 as "Patched" instead of "End-of-life," so someone somewhere must have changed it.
Was this reply relevant?
+0
-0
J.Vemmer RE: End of Life for NOD32 v4x
Secunia Official 24th Nov, 2011 15:55
Score: 5
Posts: 20
User Since: 5th Oct 2011
System Score: N/A
Location: Copenhagen, DK
We are currently working actively with ESET in order to fix this issue, and they have been as interested as we are to fix the issue.

Note that some things have changed, such as the 4.x version no longer being marked as End-of-Life.

--
Kind regards,

Jais Vemmer
xSI Signatures Specialist
Farqtronic RE: End of Life for NOD32 v4x
Member 25th Nov, 2011 14:38
Score: 0
Posts: 3
User Since: 25th Nov 2011
System Score: N/A
Location: UK
Last edited on 25th Nov, 2011 14:42
The story continues....

I have NOD32 v4.2.40.0 (home edition) installed and am now being told by Secunia PSI that my installation is insecure. Thinking that this was a little strange, I checked things out.

PSI's 'Online References' section led me to Secunia Advisory SA39736 which states that the problem is with the NOD32 'Archive Support Module' and that the solution is to update the module to version 1114.

Upon checking my own NOD32 installation, I find that I have Archive support module 1136 (20110818). i.e. an up-to-date version.

I think that Secunia PSI is telling me I have a problem where none exists due to the modular nature of NOD32. My installation may be 4.2.40.0 but the individual modules are all regularly updated by Eset.

I hope Secunia and Eset can sort this out.

Thanks.

P.S. the way Secunia's Online References linked me directly to this thread is very cool indeed. Nicely done.
Was this reply relevant?
+0
-0
J.Vemmer RE: End of Life for NOD32 v4x
Secunia Official 25th Nov, 2011 15:55
Score: 5
Posts: 20
User Since: 5th Oct 2011
System Score: N/A
Location: Copenhagen, DK
Quoting from that specific advisory (SA39736): "The vulnerability is confirmed in ESET Smart Security version 4.2.40.0 and ESET NOD32 Antivirus version 4.2.42.0. Other versions may also be affected." - These are the versions we currently use for our rules.

Please note that the latest version of the ESET NOD32 Antivirus (Home) is currently 5.x.

--
Kind regards,

Jais Vemmer
xSI Signatures Specialist
Farqtronic RE: End of Life for NOD32 v4x
Member 25th Nov, 2011 18:27
Score: 0
Posts: 3
User Since: 25th Nov 2011
System Score: N/A
Location: UK
Last edited on 25th Nov, 2011 18:31
Thank you for the reply.

I think you missed my point:

I have a valid up-to-date installation of NOD32 and Secunia PSI is suddenly giving me a false positive on a year-and-a-half old Secunia advisory.

If your advisory SA39736 is the only relevant vulnerability then, as I mentioned before, I have no problem! (check out http://kb.eset.com/esetkb/index?page=content&id=SO...).

This means, simply put, that PSI is giving me a false positive.


I don't want to upgrade to v5.x yet (see the first post of this thread) when v4.x is still fully supported by Eset and has no vulnerabilities, even according to you.

I understand that it is far more convenient for you to recommend an unnecessary update rather than fixing your own false positive but I think I have a valid point.

I hope that you can work with Eset to fix this false positive which is bad for both of your businesses.

Was this reply relevant?
+0
-0
OswaldG RE: End of Life for NOD32 v4x
Member 27th Nov, 2011 13:59
Score: 0
Posts: 4
User Since: 17th Aug 2010
System Score: N/A
Location: N/A
Farqtronic, have you tried moving to 4.2.71.2? That's the most current of the version 4 series.
Was this reply relevant?
+0
-0
Farqtronic RE: End of Life for NOD32 v4x
Member 28th Nov, 2011 20:37
Score: 0
Posts: 3
User Since: 25th Nov 2011
System Score: N/A
Location: UK
Last edited on 28th Nov, 2011 20:46
on 27th Nov, 2011 13:59, OswaldG wrote:
Farqtronic, have you tried moving to 4.2.71.2? That's the most current of the version 4 series.


Thanks for caring.

Again, my point is that a fully updated version 4.2.40.0 contains no vulnerabilities according to either Secunia advisories* or Eset.

Secunia PSI is therefore giving me a false positive. They should (together with Eset) fix that.

I am not worried about the security of my Eset installation, I'm just annoyed that I'm getting a false positive from Secunia PSI.

The crux of the problem is that due to the modular nature of NOD32, my 4.2.40.0 installation contains all modules from 4.2.71.2 as necessary. Secunia usually recognises this but they must have recently fiddled with their definitions, accidentally causing this false positive. Otherwise, why am I only now getting a warning that is based on an eighteen-month-old advisory? Does that mean I've been at risk for eighteen months?



*please read my previous posts, including the security advisory https://secunia.com/advisories/39736/ and the eset link http://kb.eset.com/esetkb/index?page=content&id=SO... for details.

Was this reply relevant?
+0
-0
Anthony Wells RE: End of Life for NOD32 v4x
Expert Contributor 29th Nov, 2011 09:58
Score: 2437
Posts: 3,327
User Since: 19th Dec 2007
System Score: N/A
Location: N/A

Hello @farqtronic ,

You have applied a "workaround" as suggested in the SA39736 by applying/updating the module . This may or may not have been part of the Secunia detection rules for the PSI ; normally , the application of a workaround is difficult to detect within the Secunia/PSI rules and may not have been a part of them whilst a fully updated version is/was not available .

It is likely that when the new edition came out and with the current possibly related Home and Pro problems that "your" version has fallen out of the PSI's detection rules .

AS you are sure your version is secure , if you do not wish to simply update and do not wish to set an ignore rule for the programme , you could be patient and wait for Secunia/Eset to gat their act together or for more instant gratification ask/mail support@secunia.com on this specific detaction of your version inclusive of the updated module .

Take care

Anthony

--


It always seems impossible until its done.
Nelson Mandela
Was this reply relevant?
+0
-0

This thread has been marked as locked.


 Products Solutions Customers Partner Resources Company
 
 Corporate
Vulnerability Intelligence Manager (VIM)
Corporate Software Inspector (CSI)
Consumer
Personal Software Inspector (PSI)
Online Software Inspector (OSI)
 Industry
Compliance
Technology
Integration
 Customers
Testimonials
 VARS
MSSP
Technology Partners
References
 Reports
Webinars
Events
 About us
Careers
Memberships
Newsroom


 
© 2002-2014 Secunia ApS - Rued Langgaards Vej 8, 4th floor, DK-2300 Copenhagen, Denmark - +45 7020 5144
Terms & Conditions and Copyright - Privacy - Report Vulnerability