Fortinet Document Library

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:


Table of Contents

Resolved Issues

The following issues have been fixed in FortiAnalyzer version 6.2.5. For inquires about a particular bug, please contact Customer Service & Support.

Device Manager

Bug ID

Description

296528 Sorting with Device Manager's Log Status column may not work properly.
496394 Users may not be able to delete a VDOM from GUI or API.
589646 FortiAnalyzer should be able to add FortiProxy device with firmware version 1.2.
596832 FortiGate Cluster is removed from log forwarding on failover when FortiAnalyzer is managed by a FortiManager.

FortiView

Bug ID

Description

562834 On FortiView > Top Sources, FortiAnalyzer displays incorrect data when trying to filter logs with Source and User.
593374 Exported PDF should take into consideration how data is sorted.
595657 Drill-down Panel for Resource Usage in SOC > FortiView may get stuck at loading.
602387 FortiAnalyzer may use high CPU resources when viewing logs from FortiGate.

Log View

Bug ID

Description

542933 FortiView does not search logs for the time entered in custom time.
550523 Downloading logs from Log View randomly fails.
596232 JSON API 3.0 logfiles/data returns adom privilege limit error if the device is secondary.
608652 Event alert logs cannot be inserted into database successfully on HA primary unit.

Others

Bug ID

Description

628352

FortiAnalyzer log-integrity check may fail.

508597 FortiAnalyzer with no devices may occupy high CPU resources by sqllogd.
529711 FortiAnalyzer may connect to map server and GeoIP server directly even when web-proxy is enabled.
551198 The command, execute restore reports-config, may not run correctly.
562540 FortiAnalyzer's diagnostic report should also include IO statistics.
568326 oftpd may keep crashing for several times a day.
569707 Device may hang and lose accessibility, including console.
590630 Backing up all ADOM logs via FTP may stop with no error printed.
591594 snmpd may frequently crash.
592593 FortiAnalyzer may update ADOM disk allocation or create ADOM without any checks when request is made via JSON API.
596192 FortiAnalyzer may return incorrect value for SNMP MIB sysObjectID.
596252 The clusterd daemon may consume high CPU resource.
597093 MIB file for FortiAnalyzer should not contain duplicated object ID.
601093 After upgrade, FortiManager may not receive logs from one FortiGate cluster that is running FortiOS 6.0.
617456 Disk space may be different between execute lvm info and other commands.

Reports

Bug ID

Description

557388 There are discrepancies in Bandwidth and Applications Report for predefined datasets on the same report time period.
588590 FortiAnalyzer should print detailed message when importing report fails.
599987 Reports may not synchronize across HA pair.
608819 Report's hcache cannot be used on scheduled report when running on specific device.

System Settings

Bug ID

Description

533885 Unnecessary message is popped up when deleting a fabric ADOM.
594693 FortiAnalyzer may show many messages on Alert Console: re-obtained table size for FGTADOM1391-Elog-1553532000 size=8192.
600639 FortiAnalyzer may not be able to move a VDOM with long name from the Root ADOM to another ADOM.
603346 FortiAnalyzer should not allow user to set to 0 day for data retention policy.
612328 When there are overlapping trust hosts, the incorrect IP and subnet might be used in the IP table.

Common Vulnerabilities and Exposures

Visit https://fortiguard.com/psirt for more information.

Bug ID CVE references

511903

FortiAnalyzer 6.2.5 is no longer vulnerable to the following CVE-Reference(s):

* CVE-2004-0230

610898

FortiAnalyzer 6.2.5 is no longer vulnerable to the following CVE-Reference(s):

* CVE-2013-5211

597311

FortiAnalyzer 6.2.5 is no longer vulnerable to the following CVE-Reference:

* CVE-2004-1653

606144

FortiAnalyzer 6.2.5 is no longer vulnerable to the following CVE-Reference:

* CVE-2019-9193

Resolved Issues

The following issues have been fixed in FortiAnalyzer version 6.2.5. For inquires about a particular bug, please contact Customer Service & Support.

Device Manager

Bug ID

Description

296528 Sorting with Device Manager's Log Status column may not work properly.
496394 Users may not be able to delete a VDOM from GUI or API.
589646 FortiAnalyzer should be able to add FortiProxy device with firmware version 1.2.
596832 FortiGate Cluster is removed from log forwarding on failover when FortiAnalyzer is managed by a FortiManager.

FortiView

Bug ID

Description

562834 On FortiView > Top Sources, FortiAnalyzer displays incorrect data when trying to filter logs with Source and User.
593374 Exported PDF should take into consideration how data is sorted.
595657 Drill-down Panel for Resource Usage in SOC > FortiView may get stuck at loading.
602387 FortiAnalyzer may use high CPU resources when viewing logs from FortiGate.

Log View

Bug ID

Description

542933 FortiView does not search logs for the time entered in custom time.
550523 Downloading logs from Log View randomly fails.
596232 JSON API 3.0 logfiles/data returns adom privilege limit error if the device is secondary.
608652 Event alert logs cannot be inserted into database successfully on HA primary unit.

Others

Bug ID

Description

628352

FortiAnalyzer log-integrity check may fail.

508597 FortiAnalyzer with no devices may occupy high CPU resources by sqllogd.
529711 FortiAnalyzer may connect to map server and GeoIP server directly even when web-proxy is enabled.
551198 The command, execute restore reports-config, may not run correctly.
562540 FortiAnalyzer's diagnostic report should also include IO statistics.
568326 oftpd may keep crashing for several times a day.
569707 Device may hang and lose accessibility, including console.
590630 Backing up all ADOM logs via FTP may stop with no error printed.
591594 snmpd may frequently crash.
592593 FortiAnalyzer may update ADOM disk allocation or create ADOM without any checks when request is made via JSON API.
596192 FortiAnalyzer may return incorrect value for SNMP MIB sysObjectID.
596252 The clusterd daemon may consume high CPU resource.
597093 MIB file for FortiAnalyzer should not contain duplicated object ID.
601093 After upgrade, FortiManager may not receive logs from one FortiGate cluster that is running FortiOS 6.0.
617456 Disk space may be different between execute lvm info and other commands.

Reports

Bug ID

Description

557388 There are discrepancies in Bandwidth and Applications Report for predefined datasets on the same report time period.
588590 FortiAnalyzer should print detailed message when importing report fails.
599987 Reports may not synchronize across HA pair.
608819 Report's hcache cannot be used on scheduled report when running on specific device.

System Settings

Bug ID

Description

533885 Unnecessary message is popped up when deleting a fabric ADOM.
594693 FortiAnalyzer may show many messages on Alert Console: re-obtained table size for FGTADOM1391-Elog-1553532000 size=8192.
600639 FortiAnalyzer may not be able to move a VDOM with long name from the Root ADOM to another ADOM.
603346 FortiAnalyzer should not allow user to set to 0 day for data retention policy.
612328 When there are overlapping trust hosts, the incorrect IP and subnet might be used in the IP table.

Common Vulnerabilities and Exposures

Visit https://fortiguard.com/psirt for more information.

Bug ID CVE references

511903

FortiAnalyzer 6.2.5 is no longer vulnerable to the following CVE-Reference(s):

* CVE-2004-0230

610898

FortiAnalyzer 6.2.5 is no longer vulnerable to the following CVE-Reference(s):

* CVE-2013-5211

597311

FortiAnalyzer 6.2.5 is no longer vulnerable to the following CVE-Reference:

* CVE-2004-1653

606144

FortiAnalyzer 6.2.5 is no longer vulnerable to the following CVE-Reference:

* CVE-2019-9193