Resolved Issues
The following issues have been fixed in FortiAnalyzer version 6.4.11. To inquire about a particular bug, please contact Customer Service & Support.
Device Manager
| Bug ID | Description |
|---|---|
| 814008 | Sort function for logs and average log rate (logs/sec) does not work in Device Manager. |
| 819664 | Under Device Manager, Average Log Rate is displayed zero for FortiGates HA Cluster. |
| 835653 | The FortiGate's IP address and firmware version are not updated when FortiGates are added manually to a non-root ADOM. |
| 837310 | FortiAnalyzer does not show the correct IP addresses and firmware versions for its registered FortiGates. |
| 838727 | Log Status of the Devices are displayed red when the Primary has a zero lograte. |
FortiView
| Bug ID | Description |
|---|---|
| 673168 | Filtering on the "Device Name" at Compromised Hosts displays "Device ID" instead. |
| 821845 | Launching Secure SD-WAN Monitor page is significantly slow, especially for viewing jitter diagram. |
| 831973 | SD-WAN Performance Status widget in Secure SD-WAN Monitor under FortiView contains blank device interfaces. |
| 841717 | The Data displayed on FortiView is inconsistent with the exported "Top Website Domains" PDF report. |
Log View
| Bug ID | Description |
|---|---|
| 765710 | When service is not in the log entry, filter based on negative service should still show related logs in the filtered result. |
Others
|
Bug ID |
Description |
|---|---|
| 817639 | FortiAnalyzer archive logs caused unexpected increase in the disk quota usage. |
| 837657 | When creating ADOMs using JSON API, default ADOM configs, such as report, datasets, and charts, are not created. |
| 838182 | Logs are not being inserted into the secondary FortiAnalyzer. |
| 839910 | The diagnose test
application oftpd command does not display any outputs for some
FortiGate devices registered on FortiAnalyzer. |
| 845871 | FortiAnalyzer stopped accepting logs and status of the devices turned into red. |
|
860113 |
The primary FortiAnalyzer can show the logs in Log View. The synchronization between primary and secondary fails and the secondary doesn't show the last logs. |
Reports
| Bug ID | Description |
|---|---|
| 764194 | Playbooks run_report fails with "missing device(s)" if "Playbook Starter" as devices filter is selected. |
|
837826 |
The event logs does not create any event logs whenever reports are being generated via "run report". |
System Settings
| Bug ID | Description |
|---|---|
| 739136 | Task monitor shows incorrect user for newly created ADOM. |
| 782431 | SNMPv3 stopped working after upgrading. |
| 837203 | Unable to fetch logs between FortiAnalyzer devices due to Invalid cross-device link error. |
| 853855 | The log forwarding filter does not seem to work properly as expected on FortiAnalyzer. |
Common Vulnerabilities and Exposures
Visit https://fortiguard.com/psirt for more information.
| Bug ID | CVE references |
|---|---|
|
839861 |
FortiAnalyzer 6.4.11 is no longer vulnerable to the following CVE Reference:
|
|
872712 |
FortiAnalyzer 6.4.11 is no longer vulnerable to the following CVE Reference:
|