PSIRTHeap Overflow in fgfmsd
Summary
A heap-based buffer overflow vulnerability [CWE-122] in FortiOS, FortiManager, FortiAnalyzer, FortiManager Cloud, FortiAnalyzer Cloud, FortiProxy fgfmd daemon may allow an authenticated attacker to execute arbitrary code or commands via specifically crafted requests.
| Version | Affected | Solution |
|---|---|---|
| FortiAnalyzer 7.6 | 7.6.0 through 7.6.2 | Upgrade to 7.6.3 or above |
| FortiAnalyzer 7.4 | 7.4.0 through 7.4.5 | Upgrade to 7.4.6 or above |
| FortiAnalyzer 7.2 | 7.2.0 through 7.2.9 | Upgrade to 7.2.10 or above |
| FortiAnalyzer 7.0 | 7.0.0 through 7.0.13 | Upgrade to 7.0.14 or above |
| FortiAnalyzer 6.4 | 6.4 all versions | Migrate to a fixed release |
| FortiAnalyzer 6.2 | 6.2 all versions | Migrate to a fixed release |
| FortiAnalyzer 6.0 | 6.0 all versions | Migrate to a fixed release |
| FortiAnalyzer Cloud 7.6 | Not affected | Not Applicable |
| FortiAnalyzer Cloud 7.4 | 7.4.1 through 7.4.5 | Upgrade to 7.4.6 or above |
| FortiAnalyzer Cloud 7.2 | 7.2.1 through 7.2.9 | Upgrade to 7.2.10 or above |
| FortiAnalyzer Cloud 7.0 | 7.0.1 through 7.0.13 | Upgrade to 7.0.14 or above |
| FortiAnalyzer Cloud 6.4 | 6.4 all versions | Migrate to a fixed release |
| FortiManager 7.6 | 7.6.0 through 7.6.1 | Upgrade to 7.6.2 or above |
| FortiManager 7.4 | 7.4.0 through 7.4.5 | Upgrade to 7.4.6 or above |
| FortiManager 7.2 | 7.2.0 through 7.2.9 | Upgrade to 7.2.10 or above |
| FortiManager 7.0 | 7.0.0 through 7.0.13 | Upgrade to 7.0.14 or above |
| FortiManager 6.4 | 6.4 all versions | Migrate to a fixed release |
| FortiManager 6.2 | 6.2 all versions | Migrate to a fixed release |
| FortiManager 6.0 | 6.0 all versions | Migrate to a fixed release |
| FortiManager Cloud 7.6 | 7.6.2 | Upgrade to 7.6.3 or above |
| FortiManager Cloud 7.4 | 7.4.1 through 7.4.5 | Upgrade to 7.4.6 or above |
| FortiManager Cloud 7.2 | 7.2.1 through 7.2.9 | Upgrade to 7.2.10 or above |
| FortiManager Cloud 7.0 | 7.0.1 through 7.0.13 | Upgrade to 7.0.14 or above |
| FortiManager Cloud 6.4 | 6.4 all versions | Migrate to a fixed release |
| FortiOS 7.6 | 7.6.0 through 7.6.2 | Upgrade to 7.6.3 or above |
| FortiOS 7.4 | 7.4.0 through 7.4.6 | Upgrade to 7.4.7 or above |
| FortiOS 7.2 | 7.2.0 through 7.2.10 | Upgrade to 7.2.11 or above |
| FortiOS 7.0 | 7.0.0 through 7.0.16 | Upgrade to 7.0.17 or above |
| FortiOS 6.4 | 6.4.0 through 6.4.15 | Upgrade to 6.4.16 or above |
| FortiOS 6.2 | 6.2 all versions | Migrate to a fixed release |
| FortiProxy 7.6 | 7.6.0 through 7.6.1 | Upgrade to 7.6.2 or above |
| FortiProxy 7.4 | 7.4.0 through 7.4.7 | Upgrade to 7.4.8 or above |
| FortiProxy 7.2 | 7.2.0 through 7.2.12 | Upgrade to 7.2.13 or above |
| FortiProxy 7.0 | 7.0.0 through 7.0.19 | Upgrade to 7.0.20 or above |
| FortiProxy 2.0 | 2.0 all versions | Migrate to a fixed release |
| FortiProxy 1.2 | 1.2 all versions | Migrate to a fixed release |
| FortiProxy 1.1 | 1.1 all versions | Migrate to a fixed release |
| FortiProxy 1.0 | 1.0 all versions | Migrate to a fixed release |
Acknowledgement
Internally discovered and reported by Gwendal Guégniaud of Fortinet Product Security team.Timeline
2025-10-14: Initial publication2025-10-15: fix affected versions