...
Warning |
---|
This page doesn't get released for the customer. The individual version release is added here however, so it is easier to see all release notes for a version. It is also easier to create the SLDM release notes by going to the Source for this page and copying the html content required. |
V5.1.2
Bug Fixes
Addressed performance issues which see up to 4 times improvement in event log processing.
Updated Desktop version to allow MSI builder to function properly.
V5.1.1
Security Updates
- Maintenance update for OpenSSL to patch to OpenSSL-1.0.2o.
- Resolved issues with the agents using TLS syslog to connect to servers with TLS 1.1 and 1.2 not negotiating correctly. The agent will now correctly negotiate up to TLS 1.2.
Bug Fixes
- There was an issue with the 'Use Host IP' installer option. Due to this issue if this option was selected during installation then it is ignored. Consequently, all the events are associated with hostname instead of Host IP. This issue is fixed in this release and now this installer option works correctly. Please note that if this option is selected during installation then the first available static IP of the machine is selected as host IP. If there is not a static IP then any first available IP is used as that host IP for syslog messages.
- Fixed an issue where UTC was being appended to local time when displaying events in the latest events page.
- This change affects warning message for license support expiry. This change updated the warning that can appear in the top right corner of the agent web UI where the message "No further events will be logged to the specified destination." will no longer be displayed if license support expires.
- Updated the agent to use the time the event was generated on the Latest Events Web UI page. Previously it was reporting the sent date/time.
- FIM configuration page has been changed so that when user selects Custom value from Schedule DDL then the custom text field would be Null instead of 'Midnight'.
- This change modifies the message from the FIM driver if network destinations are down. Earlier the message showed FIM driver was not running, in fact the driver is running but just not receiving any events as destinations are down. This change modifies the message to a more meaningful description.
- This change modifies the licensing status on the Agent page if a license is expired or support is expired when there are multiple licenses. The best license with active support is selected for setting in the agent Web UI.
...
- Maintenance update for OpenSSL to patch to OpenSSL-1.0.2n.
Bug Fixes
- Fix issue with heartbeat license messages spamming the logs with a license heatbeat every 60 minutes (if heartbeats are disabled) or every heartbeat period. Also fixed an issue with SAM issued licenses being immediately marked as expiring in 30 days and thus warning the customer that it was about to expire.
- Heartbeats events are added for the Information level to provide more information regarding the working of agent. These new heartbeats are sent when any setting is changed from GUI and when the agent service status is changed.
- This change modifies Agent behavior to not log any heartbeat if there is no SAM configured to connect. If there is a SAM configured, then to log a heartbeat if the connection is lost for every 2 hours.
- Objective matching in Snare now supports wildcards properly. In existing release of Snare in some situations this wildcard matching can cause stack overflow crash. This issue is fixed in this release and stack overflow possibility is removed during wildcard matching.
- The agent installer is capable of listing any license files it finds in the same directory as the agent executable. This change updates the agent installer to include a "None" option, to not install any license file if present.
- Fixed a bug where the Snare Agent would not import the SyslogPriority, SyslogFacility, CacheSizeSet values from an .INF (agent setup configuration file). Consequently CacheSizeEventLog was not used due to this bug.
An installation issue in the previous release of Snare may cause the installation to fail on some busy machines for 32-bit OS. Now installer properly checks the status of service operations and retries appropriately when needed.
Resolved issue where an incorrectly defined destination in Super Group Policy could prevent the agent from starting.
Some agent settings are machine specific i.e. Clientname, HostIP and HostGUID. There was an issue in the export settings command -x that was causing these machine specific settings to be exported into the .inf file and then can subsequently be loaded with /loadinf option during install. This issue is fixed in this release and now machine specific values are not exported into .inf file and even if .inf file is manually edited; these values are ignored during loadinf option.
- Fixed an issue whereby the Snare Server (via AMC) could not retrieve the master configuration from an agent using digest authentication.
...
- Maintenance update for OpenSSL to patch to OpenSSL-1.0.2m.
Bug Fixes
- Fix to send the fully qualified machine name in log message and also when generating SSL certificates.
- Update the agent to correctly display hostname when running on windows 8.1, Windows 10, Windows Server 2016.
...
- This modifies the SHA version for certificate in Windows and Unix agents. Enable higher level of security by using SHA2 support for newer version of Windows and Linux agents.
- Snare Agent web UI functionality in the agent has been modified to avoid potential cross-site scripting attack.
Bug Fixes
- Notification and warning on Snare agents has been changed to to allow syslog_5424 format on port 514. As a result of this change, notification and warning will no longer appear for valid syslog format's when using port 514.
- Fix for Snare generated events whereby host name or IP address was set to "unknown" in the message body.
- Fix a potential for memory corruption of event data being sent via TCP, TLS or UDP when under very heavy loads.
- Updated the agent to output events in utf-8 format. Some languages such as French have additional character sets as part of the locale which were not formatted correctly in UTF-8 format in the syslog message sent to third party SIEM servers. This update corrects the output of the syslog message to correctly translate the characters to utf-8 format. The browser interface to the agent will convert the characters based on the regional settings of the client system so is unaffected from this update.
- There was an issue in previous release of the snare agent where it was not properly handling the objectives during upgrade to latest release. Due to this issue, objectives may not be available after upgrade. This issue is fixed in this release and now snare properly handles the objectives during upgrade and all objectives are available after upgrade.
- Fixed a bug where if checksum for events was enabled it didn't apply the checksum correctly. Checksum may only be enabled in the registry and appends a checksum of the event. Note that checksums are applied for Snare and Syslog formats only if configured.
- Snare agent warning and notification messages has been changed to issue warning for selecting non-TAB delimiter for SNARE format(Snare Server destination). As a result of this change, new warning's will be issued when non-TAB delimited for SNARE format (for Snare Server destination) is selected.
- Resolves a bug which resulted in Windows Agent Objectives not being saved with the “Identify the event logs” as requested by the user.
...
- Maintenance update for OpenSSL to patch to OpenSSL-1.0.2j.
Bug Fixes
- Fix an issue where USB Device arrival and removal events were not correctly being picked up and sent.
- The Statistics page will no longer reset when the agent syncs with the SAM without any settings change. It will correctly display 24 hours worth of data in the graph.
- The AccessKeySet registry setting will no longer contain a valid hash if not set during the install.
- Fixed the handling of the conversion of logging levels in Group Policy when upgrading from v4 to v5.
- There was an issue that if a Snare agent and SAM are running on the same machine then Snare agent can be licensed even without configuring the SAM details in them. This issue is fixed in this release and now the SAM details should be included in the Snare agent to get it licensed from SAM.
- Host validation updated for Restrict IP when comma separated list of hosts is used
- Fix a bug where the SAM and Certificate Section of an inf file were not imported correctly by the installer
- Corrected errors related to Uninstall of the agent, where is some cases may leave a service running.
- There was an issue in the Snare Agent that was causing some settings to be marked GPO incorrectly; causing the local registry values to be ignored. The issue was specifically related to those settings that are being updated from v4 versions and upgrading to v5. The issue is fixed in this release and now Snare correctly handles the GPO source and the upgrade of settings from v4 versions when upgrading to v5.
- There was an issue the way agent handles the missing registry keys due to a corrupt configuration or a user manually removing registry keys. Due to this issue, if an agent cannot open a registry key then it just ignores it; causing snare get an error. This issue is fixed in this release. Now if snare cannot open a registry key then it creates the key with default values so that registry values can be written in newly created key. Snare logs an error if it cannot create the registry key if there is a permission problem.
...