A remote, unauthenticated cyber threat actor could exploit this vulnerability to gain access to sensitive files or take control of an affected system. At this time, all patches have been released.
A missing authentication for critical function vulnerability in FortiManager fgfmd daemon may allow a remote unauthenticated attacker to execute arbitrary code or commands via specially crafted requests.
Reports show this vulnerability is undergoing exploitation, according to a report from FortiGuard Labs.
Products affected and updates are:
- FortiManager 7.6.0, upgrade to 7.6.1 or above
- FortiManager 7.4.0 through 7.4.4, upgrade to 7.4.5 or above
- FortiManager 7.2.0 through 7.2.7, upgrade to 7.2.8 or above
- FortiManager 7.0.0 through 7.0.12, upgrade to 7.0.13 or above
- FortiManager 6.4.0 through 6.4.14, upgrade to 6.4.15 or above
- FortiManager 6.2.0 through 6.2.12, upgrade to 6.2.13 or above
- FortiManager Cloud 7.6, not affected
- FortiManager Cloud 7.4.1 through 7.4.4, upgrade to 7.4.5 or above
- FortiManager Cloud 7.2.1 through 7.2.7, upgrade to 7.2.8 or above
- FortiManager Cloud 7.0.1 through 7.0.12, upgrade to 7.0.13 or above
- FortiManager Cloud 6.4 all versions, migrate to a fixed release
Additionally, old FortiAnalyzer models 1000E, 1000F, 2000E, 3000E, 3000F, 3000G, 3500E, 3500F, 3500G, 3700F, 3700G, 3900E with the following feature enabled (FortiManager on FortiAnalyzer):
config system global
set fmg-status enable
end
At least one interface with fgfm service enabled also ends up impacted by this vulnerability.
Moreover, other than an upgrade, there are workarounds depending on the version you’re running:
For FortiManager versions 7.0.12 or above, 7.2.5 or above, 7.4.3 or above (but not 7.6.0), prevent unknown devices to attempt to register:
config system global
(global)# set fgfm-deny-unknown enable
(global)# end
This is the only workaround recommended for use in FortiManager Cloud.
Furthermore, the following is a warning: With this setting enabled, be aware if a FortiGate’s SN is not in the device list, FortiManager will prevent it from connecting to register upon being deployed, even when a model device with PSK is matching.
If FAZ features end up enabled on FMG, block the addition of unauthorized devices via syslog:
conf system global
set detect-unregistered-log-device disable
end
If FortiGate Updates or Web Filtering end up enabled, block the addition of unauthorized devices via FDS:
conf fmupdate fds-setting
set unreg-dev-option ignore
end
Alternatively, for FortiManager versions 7.2.0 and above, you may add local-in policies to whitelist the IP addresses of FortiGates that are allowed to connect.
In addition, for 7.2.2 and above, 7.4.0 and above, 7.6.0 and above it is also possible to use a custom certificate which will mitigate the issue:
config system global
set fgfm-ca-cert
set fgfm-cert-exclusive enable
Click here for more on the update.

