[CA6536] DESlock+ Client version 4.8.17 and DESlock+ Enterprise Server version 2.9.0.0 have been rolled back

Summary

ESET Customer Advisory 2017-0015

Aug 23, 2017

Severity: Critical
 

An issue found in versions of DESlock+ Client 4.8.17 and Enterprise Server 2.9.0.0 can cause unintentional encryption.

Customer Advisory

Upgrade to the latest version - End of Life notice

This article applies to version 5.x of ESET Endpoint Antivirus and ESET Endpoint Security. These products are currently in Basic Support status and are expected to reach End of Life status in December 2020. After this date, ESET Endpoint Antivirus and ESET Endpoint Security will no longer receive detection engine updates to protect against malware.

These products have been replaced on ESET download servers with DESlock+ Client version 4.8.16 and DESlock+ Enterprise Server version 2.8.0.0 to avoid potential complications. 
 

Who is affected?

If you installed DESlock+ Client 4.8.17 between August 3rd and August 24th, 2017 and performed a full disk encryption with this version, we strongly recommend that you back up all information on your systems and refrain from restarting unless you have already decrypted the system disc. There is a marginal possibility that the encryption was not done properly, which could cause your system to assume an unusable state under some circumstances. Systems on which full disk encryption was performed using earlier versions are safe, even after upgrading to the affected versions.

Solution and workaround

We expect to release updated builds of these solutions soon and apologize for any inconvenience.

Users who are already affected and who manage their DESlock+ Client using DESlock+ Enterprise Server should contact ESET or DESlock+ support immediately and ask for assistance, as it should be possible to create a unique utility for each system that reverts the problematic encryption. Standalone users who don’t use DESlock+ Enterprise Server unfortunately do not have this option.

Version log

Version 1.3 (Aug. 31st, 2017): additional information added
Version 1.2 (Aug. 29th, 2017): third version of this document