Fortinet Document Library

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.1. For inquires about a particular bug, please contact Customer Service & Support.

Bug ID Description
405484 "Attack Name" data in "Top Attacks" chart is missing XML, CSV, and CLI formats.
523875 Two FortiAnalyzer units receiving the same logs are showing sometimes significantly different log receive rates in the GUI.
523886 ADOM override may not be applied correctly for the log section.
524097 When viewing or editing ADOM quotas in Storage Info, the frame may need 10 to 15 seconds to load.
526167 Subnet filter should be supported in real time log view and it should not return "no entry found".
527075 Collector mode Log View with log forwarding enabled may return "No entry found".
527076 Application name in FortiView is truncated if _ is used in the service name.
532728 Threat Map is not displayed due to missing longitude and latitude configurations in Device Manager for a FortiGate.
540000 The number of log fields for FortiManager event logs displayed in FortiAnalyzer's Log View is less as compared to FortiManager.
541820 The bandwidth-app-Top-Dest-By-Bandwidth-Sessions dataset should not split similar destinations into two different distinct destinations.
542475 FortiView > Traffic > Policy Hits shows a mix of policy name and policy ID.
544197 VDOM name may be missing a digit when adding a device with a long name.
545509 Remote logging towards FortiAnalyzer should not saturate the number of admin logins on a MBD/FPC slot.
547904 Cluster Members status may be showing both nodes as connection down.
548841 Add command on FortiAnalyzer to breakdown lograte by ADOMs.
549915 Completed reports with long names are not being displayed under Report Folders.
550235 FTPS protocol should have archive data link for DLP.
552610 FortiAnalyzer cannot save email address in the "From" field on Incidents & Events when TLD has five or more characters.
552614 The "Log Insert Lag Time" widget may not show data, creating cut-offs on the graph.
553500 Log forwarding with "All" device filter may stop after upgrade.
554116 FortiAnalyzer may not be able to receive logs from FortiGate 5.6 cluster.
554345 FortiAnalyzer may consistently generate event logs stating "Did not receive any log" for devices that changed from standalone to HA.
554890 Log events should consistently end with a dot (.) delimiter.
555944 FTP upload should be working at the specified time defined for upload.

556523

FortiGate running 5.4 may close OFTP connection to FortiAnalyzer 6.2.

557407 Automatic Quarantine may not be applied to FortiSwitch.
558084 FortiAnalyzer should not generate logs stating "Can not find user:admin when running report:1000060025".
558348 FortiAnalyzer is showing inconsistency in the listed report owner when cloning and importing a report.

559662

Report configuration may not be saved because wildcard admin user name is too long.

562220 The "diagnose dvm check-integrity" command may not be able to fix errors caused by missing device databases.

564610

With ADOMs disabled, predefined scheduled reports still run on non-root ADOMs.

566495

After added log facility for log-forward setting via CLI, the change may not reflected in log data.

Common Vulnerabilities and Exposures

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

Vulnerability

FortiAnalyzer 6.2.1 is no longer vulnerable to the issue described in the following link - https://fortiguard.com/psirt/FG-IR-19-144.

Resolved Issues

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

Bug ID Description
405484 "Attack Name" data in "Top Attacks" chart is missing XML, CSV, and CLI formats.
523875 Two FortiAnalyzer units receiving the same logs are showing sometimes significantly different log receive rates in the GUI.
523886 ADOM override may not be applied correctly for the log section.
524097 When viewing or editing ADOM quotas in Storage Info, the frame may need 10 to 15 seconds to load.
526167 Subnet filter should be supported in real time log view and it should not return "no entry found".
527075 Collector mode Log View with log forwarding enabled may return "No entry found".
527076 Application name in FortiView is truncated if _ is used in the service name.
532728 Threat Map is not displayed due to missing longitude and latitude configurations in Device Manager for a FortiGate.
540000 The number of log fields for FortiManager event logs displayed in FortiAnalyzer's Log View is less as compared to FortiManager.
541820 The bandwidth-app-Top-Dest-By-Bandwidth-Sessions dataset should not split similar destinations into two different distinct destinations.
542475 FortiView > Traffic > Policy Hits shows a mix of policy name and policy ID.
544197 VDOM name may be missing a digit when adding a device with a long name.
545509 Remote logging towards FortiAnalyzer should not saturate the number of admin logins on a MBD/FPC slot.
547904 Cluster Members status may be showing both nodes as connection down.
548841 Add command on FortiAnalyzer to breakdown lograte by ADOMs.
549915 Completed reports with long names are not being displayed under Report Folders.
550235 FTPS protocol should have archive data link for DLP.
552610 FortiAnalyzer cannot save email address in the "From" field on Incidents & Events when TLD has five or more characters.
552614 The "Log Insert Lag Time" widget may not show data, creating cut-offs on the graph.
553500 Log forwarding with "All" device filter may stop after upgrade.
554116 FortiAnalyzer may not be able to receive logs from FortiGate 5.6 cluster.
554345 FortiAnalyzer may consistently generate event logs stating "Did not receive any log" for devices that changed from standalone to HA.
554890 Log events should consistently end with a dot (.) delimiter.
555944 FTP upload should be working at the specified time defined for upload.

556523

FortiGate running 5.4 may close OFTP connection to FortiAnalyzer 6.2.

557407 Automatic Quarantine may not be applied to FortiSwitch.
558084 FortiAnalyzer should not generate logs stating "Can not find user:admin when running report:1000060025".
558348 FortiAnalyzer is showing inconsistency in the listed report owner when cloning and importing a report.

559662

Report configuration may not be saved because wildcard admin user name is too long.

562220 The "diagnose dvm check-integrity" command may not be able to fix errors caused by missing device databases.

564610

With ADOMs disabled, predefined scheduled reports still run on non-root ADOMs.

566495

After added log facility for log-forward setting via CLI, the change may not reflected in log data.

Common Vulnerabilities and Exposures

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

Vulnerability

FortiAnalyzer 6.2.1 is no longer vulnerable to the issue described in the following link - https://fortiguard.com/psirt/FG-IR-19-144.