Resolved Issues
The following issues have been fixed in FortiAnalyzer version 7.0.10. To inquire about a particular bug, please contact Customer Service & Support.
Device Manager
Bug ID | Description |
---|---|
861979 | FortiAnalyzer generates "Invalid user/password for Security Fabric device in Device manager" even though the password is correct. |
FortiSOC
Bug ID | Description |
---|---|
685263 783407 |
Playbook failed to get software inventory from EMS server when site is enabled on EMS server. |
783569 | Automation Stitch Action "Ban IP" does not work on FortiGate because FortiAnalyzer did not send the srcip to FortiGate. |
FortiView
Bug ID | Description |
---|---|
783408 | When selecting 'IPSec VPN' login type under the 'Top Failed Authentication' tab, it displays No Results. |
954773 | Top Threat Destinations widget doesn't show expected data according to selected TOP Numbers. |
Log View
Bug ID | Description |
---|---|
860990 | In the Log View section, the log file's sorting function does not work, and the arrow icon is missing. |
Others
Bug ID | Description |
---|---|
893699 | Login failed for restapi request due to invalid user/password. |
951791 |
Continuous crashes for the "fileparsed Application" on FortiAnalyzer HA have been observed. |
952295 | FortiAnalyzer does not remove the logs after forwarding then to the cloud storage. |
Reports
Bug ID | Description |
---|---|
936084 | No data is showed up in report when filter applied to chart in FortiMail ADOM. |
System Settings
Bug ID | Description |
---|---|
927773 |
When specific ADOMs are selected as Filters, Log Forwarding stops functioning. |
Common Vulnerabilities and Exposures
Visit https://fortiguard.com/psirt for more information.
Bug ID | CVE references |
---|---|
904375 |
FortiAnalyzer 7.0.10 is no longer vulnerable to the following CVE Reference:
|
928114 |
FortiAnalyzer 7.0.10 is no longer vulnerable to the following CVE Reference:
|
941847 |
FortiAnalyzer 7.0.10 is no longer vulnerable to the following CVE Reference:
|
949991 |
FortiAnalyzer 7.0.10 is no longer vulnerable to the following CVE Reference:
|