Resolved Issues
The following issues have been fixed in 6.4.13. To inquire about a particular bug, please contact Customer Service & Support.
AP Manager
|
Bug ID |
Description |
|---|---|
|
892773 |
Assigning AP Profile returns invalid value. |
Device Manager
| Bug ID | Description |
|---|---|
| 768289 | There is a discrepancy in the usage of quotation marks ("") when configuring DHCP relay from FortiManager or retrieving it from FortiGate. |
| 910391 | When FortiManager operates in a non-default workspace mode, it may attempt to purge the configuration of the FortiGate devices due to database corruption. |
|
917810 |
FortiManager displays an event log with the "update temp cachedb failed" error message when changing the FortiGate management VDOM to |
Others
|
Bug ID |
Description |
|---|---|
|
921233 |
Azure Fabric Connector Credential does not push to the Azure VM FortiGate, when Azure Fabric connector is created on FortiManager without a managed identity. |
Policy and Objects
|
Bug ID |
Description |
|---|---|
| 696367 | Hit count, first used, and last used may not get updated on FortiManager. |
| 814468 | FortiManager purges "gcp-project-list" and unsets several values from GCP sdn-connector. |
| 846222 | Unable to perform the policy diff when both device and policy package are locked. |
| 902298 | FortiManager does not generate error messages when invalid or obsolete application IDs are used in the policy. Instead, it allows installation and sets the category to "pass" or "monitor". |
System Settings
|
Bug ID |
Description |
|---|---|
|
848934 |
SNMPv3 does not work properly on FortiManager and FortiAnalyzer. |
Common Vulnerabilities and Exposures
Visit https://fortiguard.com/psirt for more information.
| Bug ID | CVE references |
|---|---|
|
921579 |
FortiManager 6.4.13 is no longer vulnerable to the following CVE Reference:
|
|
922503 |
FortiManager 6.4.13 is no longer vulnerable to the following CVE Reference:
|
|
934151 |
FortiManager 6.4.13 is no longer vulnerable to the following CVE Reference:
|