19.0 Fixed Issues
The following is a list of the most relevant fixed issues in the 19.0 GA release. Many of the issues below were included in Service Packs leading up to this version. To see additional issues and enhancements that were included in 19.0, see the links to the Service Packs below, and refer to issues that have a ‘19.0’ version label.
Item |
Area |
Relevant OS |
Description |
Component |
|---|---|---|---|---|
CYBR-17063 |
Custom Rules |
All |
When editing rule names in the Custom rules screen, if the rule name is too long, it does not display correctly and requires you to hover to see the full name. After this fix, the entire rule name displays correctly. |
Server |
CYBR-16471 |
Malop Inbox |
All |
Malops on the same machine that were related to PowerShell processes were not grouped into one Malop. After the fix, such Malops are grouped correctly. |
Server |
CYBR-17049 |
Malop Inbox |
All |
In the Malop Inbox, if you had a large number of Malop labels that extended past the bottom of the screen, you could not scroll to view additional labels and were forced to zoom out to view them all. After this fix, it is possible to scroll to view all Malop labels. |
Server |
CYBR-18259 |
Malop Inbox |
All |
When adding Malop comments through the API, such as through Demisto commands or other automation scripts, Malops became corrupted in the database as the API command does not contain the Malop management status. Therefore, Malop alerts were not sent correctly. After this fix, even when you add a comment through the API, the Malop status is reflected correctly and alerts are sent correctly. |
Server |
CYBR-16670 |
NGAV |
Windows |
On the latest versions of the Sensor, after uninstalling the Application Control service, the service continued to run and the driver for the service was not uninstalled correctly. After this fix, uninstallation removes the driver as intended and stops the service. |
Sensor |
CYBR-16757 |
NGAV |
Windows |
After installing the latest 17.6 version of the Sensor with installation flags set, in the System > Sensors screen, when the Anti-Malware mode was disabled by switching the toggle option to Off, the Anti-Malware > Signatures mode on the Sensor displayed as as Detect. After this fix, when installing if the Anti-Malware mode is set to Off in the System > Sensors screen, the Signatures mode is set to Disabled. |
Server |
CYBR-16314 |
Reputations |
All |
After updating a process reputation in the Cybereason UI, the reputation was not updated across all Detection servers correctly and Malops, suspicion, and evidence continued to be associated with the item with a reputation update. This was due to a database corruption for the reputation file. After this fix, we have added a mechanism to fix this type of scenario. |
Server |
CYBR-18090 |
Sensor Installation |
Linux |
When trying to upgrade Sensors for Linux, the upgrade left the previous Sensor version on the machine because of a problem reading and closing one of the files required for upgrade. After this fix, the installation configuration was updated to make sure this file close issue is resolved and the upgrade is performed successfully. |
Sensor |
CYBR-12905 |
Sensor Performance |
Linux |
When collecting information on Linux machines which were abundant with short-lived connections, the connection info collection sometimes made machines experience CPU spikes. After this fix, we have updated the Linux sensor configuration to mitigate and limit these CPU spikes. |
Linux |
CYBR-19369 |
Sensor Performance |
Mac |
When installing the recent version of the Sensor with the proxy configuration using a PAC file, the connection failed. After this fix, the Sensor is able to connect with the proxy settings without a problem. |
Sensor |
CYBR-16386 |
Sensor Tagging |
Windows |
18.1.50 After upgrading, sensor tags were missing. After the fix, sensor tags are not missing after upgrades. |
Server |