Resolved issues
The following issues have been fixed in 7.0.10. For inquires about a particular bug, please contact Customer Service & Support.
AP Manager
| Bug ID | Description |
|---|---|
|
861941 |
FortiManager Cloud attempts to install " |
| 889811 |
Under WIFI and switch controller for Managed FortiAPs there is not any LLDP info found. |
Device Manager
|
Bug ID |
Description |
|---|---|
| 472443 | FortiManager Cloud does not retrieve any of
the profiles and addresses in the format of "g-XXX" from FortiGates when
VDOMs are enabled. |
| 723720 | "strong-crypto" feature change
under the CLI configuration cannot be installed to FortiGate. |
| 811104 | Import policy package fails after installing web-proxy through CLI configurations. |
| 949546 | When assigning interfaces to a zone in a vdom, it is not visible in Device Manager. |
| 949646 |
Static route changes made in FortiManager Cloud do not appear in the installation preview. |
Others
| Bug ID | Description |
|---|---|
| 813443 | FortiManager Cloud does not support the FGT-GCP different IP addresses on interfaces and different source DNS IP. |
| 891253 | The firmware upgrade is successful; however, the task line does not get updated for the retrieve action when device names exceed the predefined character limit. |
| 941203 | FortiManager Cloud does not support the use of Certificate Templates to create certificates with a "range=global" setting for FortiGates operating in multi-vdom mode. |
Policy and Objects
| Bug ID | Description |
|---|---|
|
468776 825873 |
FortiManager Cloud does not support FortiGate/FortiOS global scope (g-) objects. |
| 630648 | A FortiManager Cloud instance running on Microsoft Azure is unable to import the SDN connector for a dynamic firewall address and is displaying an error message stating "wrong input parameter." |
| 696367 | Hit count, first used, and last used may not get updated on FortiManager Cloud. |
| 725427 | Policy package install skips the policy where destination interface is set as SD-WAN zone and policy is IPSEC policy. |
| 793240 |
FortiManager Cloud fails to retrieve FortiGate's configuration when external-resource objects include a "g-" prefix. |
| 855073 |
The "where used" feature does not function properly. |
| 875103 | Local categories gets purged if used in Profile Mode Security Profiles. |
| 889586 | Azure Service Tags not displayed correctly in FortiManager Cloud. |
| 894597 | Default value for
"unsupported-ssl-version" in ssl-ssh-profile gets modified during
the installation. |
| 899226 | Unable to create Central SNAT explicit port translations on FortiManager Cloud. |
| 914945 | Unable to modify or clone the "SSL/SSH inspection profile" in the Policy & Object on the ADOM 7.0 version. |
| 920983 | The policy blocks using a group object do not get updated when the objects within the group are modified. |
| 924680 | Policy packages containing geo-based ISDB objects may not be successfully installed to the FortiGates. |
| 942659 | Syncing EMS tags from FortiManager Cloud fails when the EMS Connector is configured in multi-site mode. |
Revision History
| Bug ID | Description |
|---|---|
|
904710 |
Restoring a revision of a policy removes the information of all the SD-WAN rules. |
Script
| Bug ID | Description |
|---|---|
|
931196 |
Scheduled Scripts created by the ldap users cannot be run and FortiManager Cloud displays "Data is not ready" error message. |
System Settings
| Bug ID | Description |
|---|---|
| 842732 | FortiManager Cloud does not display the Secondary HA member's status correctly. |
| 936694 | After removing a device, FortiManager Cloud generates repeated "sync dvmdb to faz" tasks for all logged-in administrative users. |
Common Vulnerabilities and Exposures
Visit https://fortiguard.com/psirt for more information.
| Bug ID | CVE references |
|---|---|
|
904375 |
FortiManager Cloud 7.0.10 is no longer vulnerable to the following CVE Reference:
|
|
928114 |
FortiManager Cloud 7.0.10 is no longer vulnerable to the following CVE Reference:
|
|
941847 |
FortiManager Cloud 7.0.10 is no longer vulnerable to the following CVE Reference:
|