CVE-2024-26011: FortiOS - Improper authentication in fgfmd
A missing authentication for critical function vulnerability in Fortinet FortiManager 7.4.0 through 7.4.2, FortiManager 7.2.0 through 7.2.4, FortiManager 7.0.0 through 7.0.11, FortiManager 6.4.0 through 6.4.14, FortiOS 7.4.0 through 7.4.3, FortiOS 7.2.0 through 7.2.7, FortiOS 7.0.0 through 7.0.14, FortiOS 6.4 all versions, FortiOS 6.2 all versions, FortiOS 6.0 all versions, FortiPAM 1.2 all versions, FortiPAM 1.1 all versions, FortiPAM 1.0 all versions, FortiPortal 6.0.0 through 6.0.14, FortiPortal 5.3 all versions, FortiProxy 7.4.0 through 7.4.3, FortiProxy 7.2.0 through 7.2.9, FortiProxy 7.0.0 through 7.0.16, FortiProxy 2.0 all versions, FortiProxy 01.02 all versions, FortiProxy 1.2 all versions, FortiProxy 01.01 all versions, FortiProxy 1.1 all versions, FortiProxy 01.00 all versions, FortiSwitchManager 7.2.0 through 7.2.3, FortiSwitchManager 7.0.0 through 7.0.3 allows attacker to execute unauthorized code or commands via specially crafted packets.
Other sources
An improper authentication vulnerability [CWE-287] in FortiManager, FortiOS, FortiPAM, FortiPortal, FortiProxy and FortiSwitchManager fgfmd daemon may allow an unauthenticated attacker to inject (but not receive) packets in tunnels established between a FortiManager and the targeted device.
— FortiGuard
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
FortiManagerto a version that resolves this vulnerability.Fixed in 6.4.15 - Upgrade
Upgrade
FortiManagerto a version that resolves this vulnerability.Fixed in 7.0.12 - Upgrade
Upgrade
FortiManagerto a version that resolves this vulnerability.Fixed in 7.2.5 - Upgrade
Upgrade
FortiManagerto a version that resolves this vulnerability.Fixed in 7.4.3 - Upgrade
Upgrade
FortiOSto a version that resolves this vulnerability.Fixed in 7.0.15 - Upgrade
Upgrade
FortiOSto a version that resolves this vulnerability.Fixed in 7.2.8 - Upgrade
Upgrade
FortiOSto a version that resolves this vulnerability.Fixed in 7.4.4 - Upgrade
Upgrade
FortiOSto a version that resolves this vulnerability.Fixed in 7.6.0 - Upgrade
Upgrade
FortiPAMto a version that resolves this vulnerability.Fixed in 1.3.0 - Upgrade
Upgrade
FortiPortalto a version that resolves this vulnerability.Fixed in 6.0.15 - Upgrade
Upgrade
FortiProxyto a version that resolves this vulnerability.Fixed in 7.0.17 - Upgrade
Upgrade
FortiProxyto a version that resolves this vulnerability.Fixed in 7.2.10 - Upgrade
Upgrade
FortiProxyto a version that resolves this vulnerability.Fixed in 7.4.4 - Upgrade
Upgrade
FortiSwitchManagerto a version that resolves this vulnerability.Fixed in 7.0.4 - Upgrade
Upgrade
FortiSwitchManagerto a version that resolves this vulnerability.Fixed in 7.2.4 - Upgrade
Upgrade
FortiVoiceto a version that resolves this vulnerability.Fixed in 6.4.9 - Upgrade
Upgrade
FortiVoiceto a version that resolves this vulnerability.Fixed in 7.0.2 - Upgrade
Upgrade
FortiWebto a version that resolves this vulnerability.Fixed in 7.4.3 - Upgrade
Upgrade
FortiWebto a version that resolves this vulnerability.Fixed in 7.6.0 - Upgrade
Upgrade
FortiAuthenticatorto a version that resolves this vulnerability.Fixed in 7.0.0
Event History
Frequently Asked Questions
What is the severity of CVE-2024-26011?
The severity of CVE-2024-26011 is critical due to the missing authentication for critical functions.
How do I fix CVE-2024-26011?
To fix CVE-2024-26011, upgrade FortiManager to version 7.4.3 or later, FortiOS to 7.4.4 or later, or FortiProxy to version 7.4.4 or later.
Which versions of Fortinet products are affected by CVE-2024-26011?
CVE-2024-26011 affects multiple versions of FortiManager, FortiPAM, FortiProxy, and FortiOS between specific version ranges.
How can I determine if my Fortinet product is vulnerable to CVE-2024-26011?
You can determine vulnerability by checking if your Fortinet product version matches any of the affected versions listed in CVE-2024-26011.
Are there any workarounds for CVE-2024-26011 before patching?
There are no known workarounds for CVE-2024-26011, so upgrading to the latest version is recommended as the only mitigation.