Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

Kaspersky identifiying TB as vulnerable - what should I do?

  • 4 svar
  • 1 har detta problem
  • 18 visningar
  • Senaste svar av Matt

more options

Have used TB and Kaspersky together for years but this last scan has shown Kaspersky regards TB as a vulnerable application and advises upgrade to latest version but I am on latest version. Windows 10 and TB 60.9.1. Is this a known issue please?

Have used TB and Kaspersky together for years but this last scan has shown Kaspersky regards TB as a vulnerable application and advises upgrade to latest version but I am on latest version. Windows 10 and TB 60.9.1. Is this a known issue please?

Vald lösning

There is a version 68. But not all users have been targetted yet to be updated. If you are not having troubles on version 60 I wouldn't worry about not being on 68.

Question - are you using the Pro version of Kaspersky?

Läs svaret i sitt sammanhang 👍 1

Alla svar (4)

more options

Further info re above message. Vulnerability code is 11591

more options

Vald lösning

There is a version 68. But not all users have been targetted yet to be updated. If you are not having troubles on version 60 I wouldn't worry about not being on 68.

Question - are you using the Pro version of Kaspersky?

more options

Thanks Wayne. Not using the Kaspersky Pro version. The only other issue Kaspersky seems to have with Thunderbird - had it for a long time - is that it "cannot guarantee the authenticity of the domain to which the encrypted connection is established" Application Thunderbird - URL nic-nac-project.org As neither this nor the vulnerable application seem to cause any problems - nothing shows on scans for viruses/ malware / spyware etc I shall just ignore.

more options

Your issue with the nic nac project is that the update URL included in the add-on you have installed from that site in not using SSL. It is not really an issue as none of the add-ons from that site have been updated for V68, so they will be disabled on update anyway.