The following issues were resolved in the Network Security 10.0.0 release.
Tracking number | Summary |
|---|---|
COM-12986 | New logs could not be generated due to the Log Manager Create button being disabled and the progress showed "Archive being created". The issues are resolved. |
COM-23960 | The physical disk serial number did not match the output of |
COM-29773 | Upgrading previously created certs under FireEye org name is not supported. |
COM-29806 | Power supply failure alert notifications were created unnecessarily in the following models: NX 3500, NX 4500, NX 5500. This issue is resolved |
COM-29863 | Apache has been upgraded to overcome the vulnerability described in IAVM 2022-A-0124. |
COM-29874 | Vulnerabilities CVE-2022-22965, CVE-2022-22963, and CVE-2022-22950 are resolved. |
COM-29002 | The show log continuous command was not generating the expected output. The issue is resolved. |
COM-29377 | The Velocity Engine has been upgraded to address the Velocity Sandbox Bypass issue (CVE-2020-13936). |
COM-29624 | Some appliances could not connect to HelixConnect. This issue is resolved. |
COM-29702 | CEF logs did not have the cs6 field extension. This issue is resolved. |
COM-30030 | Alert notifications and alert logs were delayed when many detections occurred simultaneously. This issue is resolved. |
COM-30031 | The Apache vulnerability described in IAVM 2022-A-0230 has been addressed. |
COM-30144 | The SMTP alerts using TLS failed to authenticate if the password contained a |
COM-30244 | mgmtd could not be recovered if a failure occurred. The issue is resolved. mgmtd can now be recovered by rebooting the system after a failure. |
COM-30325 | SNMP settings used to reset to default values on reloading the site or logging out. The issue is resolved. |
COM-30344 | TLS version 1.1 was not secure enough in compliance mode for CC-NDcPP 2022 certification. The issue is resolved. TLS is upgraded to version 1.2. |
COM-30537 | CVE-2021-46848 vulnerability has been addressed. |
COM-30604 | Delimiter between multiple SSH Allow users was not effective. The issue was resolved. |
COM-30641 | The full file path was included in the "filename" field in the metadata that was sent to cloud.fireeye.com. This issue has been resolved. |
COM-30743 | License update was producing the error message, "Internal error fetching licenses". The issue is resolved. |
COM-30788 | You can now view datastreaming logs from the CLI using the |
COM-30894 | Issues of generating empty static reports have been fixed. |
COM-30935 | SNMPv3 allowed the creation of a user with an invalid SNMP key. This issue is resolved. |
COM-30950 | The original file names were being truncated in the malware analysis table during local and remote transfer. The issue is resolved. |
COM-31007 | Apache has been upgraded to overcome the vulnerability described in CVE-2023-24998. |
COM-31187 | Advanced URL Defense reported an error on the sensor appliance. The issue is resolved. |
WEBMPS-21636 | Issues related to backup, restore and reset factory settings for IPS services are resolved.
|
WEBMPS-21803 | The NX 6500 appliance showed incorrect Warning and Critical values for Maximum bandwidth in both the CLI and the Web UI. The issues are resolved. |
WEBMPS-24145 WEBMPS-24841 | Security Content update failure did not trigger an SNMP trap. The issue is resolved. |
WEBMPS-24321 | System Load and other services were generating false health alerts. The issues are resolved. |
WEBMPS-24531 | ifName was not included in the interface-up / interface-down SNMP trap. This issue is resolved. |
WEBMPS-24836 | The Network Security appliance could not cancel an active packet capture service. The issue is resolved. |
WEBMPS-24884 | Source and destination IP addresses appeared interchanged on the Alert Details page and in XML and CSV files. The issue is resolved. |
WEBMPS-25062 | An issue created by the escape characters '\/\/' in urllist.txt is resolved. |
WEBMPS-25104 | Riskware alert severity was displayed as N/A on the Web UI Dashboard. This issue is resolved. |
WEBMPS-25170 | The Network Security appliance in L3 mode was sending reset packets while the port-pairs were in TAP mode. This issue is resolved |
WEBMPS-25195 | Inconsistencies in alerts from the Network Security appliance and Helix are resolved. |
WEBMPS-25426 | 250-****STARTTLS response instead of 250-STARTTLS was not accepted on the Network Security appliance. This issue has been resolved. |
WEBMPS-25615 | Proxy details were missing in the riskware alert notification. The issue is resolved. |
WEBMPS-25679 | The Network Security appliance was receiving empty IP address on configuring drop out-interface. The issue is resolved. You need to execute policymgr interface re-configure CLI command after configuring any policymgr interface commands. |
WEBMPS-25806 | A database corruption event created multiple issues on the Network Security 1500 appliance. These issues are resolved. |
WEBMPS-26034 | Change in timezone was not being honoured by the Service Health Digest notification. This issue is resolved |
WEBMPS-26238 | IPS custom rule validation failed for rules with UDP protocol and the TCP flags option. This issue is resolved. |
WEBMPS-26249 | 'Backup Reserve/free spaces is too low' error was logged when generating a backup config+fedb even though disk space is enough to store more backups. This issue is resolved. |
WEBMPS-26413 | The disk space under /var/root/tmp/sa_python was full. The issue is resolved. |
WEBMPS-26418 | SSL connection was timing out due to delayed SYN ACK on the Network Security appliance. The issue is resolved. |
WEBMPS-26426 | Inconsistency in ICAP blocking is resolved. |
WEBMPS-26439 | Issues arising due to a TCP evasion technique are resolved. The evasion technique works by overlapping a TCP segment with a fake packet. |
WEBUI-14724 | Naming a custom dashboard using non-ASCII and hyphen characters failed on the Web UI with the following error message: "Please enter a valid name". This issue is resolved. |
WEBUI-14821 | When an IPS event was clicked on the Web UI, the page did not respond. IPS performance improvement has fixed this issue. |