Description | This article describes the necessary steps to mitigate the vulnerability CVE-2024-48887 [FG-IR-24-435]. |
Scope | FortiSwitch v6.4, v7.0, v7.2, v7.4, v7.6. |
Solution |
FortiSwitch is affected by this vulnerability only if its GUI (HTTP/HTTPS) is accessible to unauthorized devices.
Even when FortiSwitch is managed, it remains vulnerable only if there is a policy or route configured that originates from the FortiLink interface and allows access to the FortiSwitch GUI from an external network.
As stated in Fortinet PSIRT Advisory PSIRT Unverified password change via set_password endpoint (FG-IR-24-435), the recommended workaround is to disable HTTP/HTTPS access and configure trusted hosts.
config system admin
Configuring Trusted Hosts on Managed FortiSwitch. The below config is done on the FortiGate and applied to FortiSwitch: Refer to 'Executing custom FortiSwitch scripts'.
config switch-controller custom-command
config switch-controller managed-switch edit "S524DF4K1XXXXXXX" config custom-command edit 1 set command-name "trusthost1" next end next end
Note: The above example shows how to allow access to FortiSwitch from the 10.255.1.0/24 subnet, which is here assumed to be the FortiLink subnet.
Note for Managed FortiSwitch: Disabling HTTPS access on a FortiSwitch that is managed by a FortiGate is not recommended because configuration push from FortiGate to FortiSwitch relies on port 443 (HTTPS). Disabling HTTPS in this scenario would prevent configuration synchronization and management.
Best Recommendation: Upgrade FortiSwitch to a Fixed Version.
FortiSwitch v7.6.0 → Upgrade to v7.6.1 or above. |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.