June 21, 2020 Service Pack
The following Service Pack versions were released:
Versions (Sensor and Server) |
|---|
18.0.340 18.1.260 19.0.201 19.1.201 19.2.101 |
The tables below describe the enhancements, fixed issues, and changes included in each version.
The Versions column indicates the versions that include the fix.
The Required Update column indicates if the fix requires sensor/server update.
IMPORTANT: If you want to upgrade your servers to this version, we recommend that you upgrade all components - Registration server, Detection servers, and WebApp server - to this version.
Enhancements
Issue |
Area |
Description |
Versions |
Required Update |
Sensor OS |
|---|---|---|---|---|---|
CYBR-30402 |
Configuration |
To enhance customization, it is now possible to enable different proxy settings (for all sensors) for communication between the sensor and the Detection server. This can be enabled by the Technical Support team via sensor personalization. |
19.1.201, 19.2.101 |
Sensor |
Linux |
CYBR-28798 |
Detection |
We have improved performance by optimizing the way sensors collect information about process modules. |
18.0.340, 18.1.260, 19.0.201 |
Sensor |
Windows |
CYBR-29388 |
NGAV |
If the name of a process was missed during collection, we have made an enhancement to .NET/PowerShell detection to provide the name of the process within the Malop. |
18.0.340, 18.1.260, 19.0.201 |
Sensor |
Windows |
CYBR-27951 |
NGAV |
We have made security improvements to our NGAV component. |
18.0.340, 18.1.260, 19.0.201 |
Sensor |
Windows |
CYBR-27865 |
OS Support |
Cybereason now supports sensor installation on RHEL 8 and CentOS 8. |
18.0.340, 18.1.260, 19.0.201 |
Server |
N/A |
Fixed issues
Issue |
Area |
Description |
Versions |
Required Update |
Sensor OS |
|---|---|---|---|---|---|
CYBR-30573 |
Detection |
When processing collected connections data, the sensor sent messages to the Detection server without required fields. This issue has been resolved. |
18.0.340, 18.1.260, 19.0.201, 19.1.201, 19.2.101 |
Sensor |
Windows |
CYBR-30286 |
Detection |
The process image file name can be changed several times during the process lifecycle. If this occurred, the sensor ignored it. This issue has been resolved. |
18.0.340, 18.1.260, 19.0.201 |
Sensor |
Windows |
CYBR-30572 |
Detection |
The Detection server now ignores corrupted messages sent from sensors, improving performance and stability. |
18.1.260, 19.0.201 |
Server |
N/A |
CYBR-28993 |
Endpoint Controls |
Malware alerts contained inaccurate descriptions and states. This issue has now been resolved. |
19.2.101 |
Sensor |
Mac |
CYBR-30155 |
NGAV |
When upgrading a sensor, the upgrade did not include the correct versions of the DLLs. This issue has now been resolved. We have also improved the way the NGAV feature accesses the Cybereason driver. |
19.0.201 |
Sensor |
Windows |
CYBR-26401 |
NGAV |
A mistake in the translation for detection classification within Application Control and static analysis was fixed. |
18.0.340, 18.1.260, 19.0.201, 19.1.201, 19.2.101 |
Server |
N/A |
CYBR-30933 |
NGAV |
To reduce the number of false positives from the Behavioral document protection feature, we no longer create Malops from the document opening process. |
19.2.82, 19.2.83, 19.2.101 |
Server |
Windows |
CYBR-30578 |
Sensor Management |
Due to an OpenSSL issue, sensors crashed on machines with 10th Gen Intel Core processors. This issue has now been resolved. |
19.1.201, 19.2.101 |
Sensor |
Linux, Mac |
CYBR-31881 |
Sensor Management |
On the System > Sensor screen, if a query for Online sensors with an Internal IP was run multiple times, the results would return empty, even if such sensors existed. This issue has been resolved. |
19.0.201, 19.1.201, 19.2.101 |
Server |
All |
CYBR-31078 |
Sensor Management |
When cloning a machine with a sensor, if the original template had not connected to the Registration server and the server.host registry key was empty before the clone deployment, the sensor crashed and did not recover. This issue was resolved. |
18.0.340, 18.1.260, 19.0.201, 19.1.201, 19.2.101 |
Sensor |
Windows |
CYBR-29495 |
Sensor Management |
If a disconnected sensor received multiple action requests, the initial request could not be aborted or dismissed. This issue has been resolved. |
19.0.201 |
Server |
N/A |
CYBR-24292 |
Sensor Management |
If too many waiting or pending actions were queued, the sensor action log did not clear old completed actions. This issue has been resolved and the rules for creating actions within the log have been improved. |
19.0.201 |
Server |
N/A |
CYBR-29796 |
Sensor Management |
The email notification for archived sensors included both the total number archived sensors and the number of sensors to be archived in the next 24 hours. This issue has been resolved. The email notification will now only contain the number of sensors to be archived in the next 24 hours. |
19.0.201 |
Server |
N/A |
CYBR-25969 |
Sensor Management |
In the System > Sensors screen, it was not possible to sort sensors by policy fields, such as Assigned policy. This issue has been resolved. |
19.1.201, 19.2.101 |
Server |
N/A |