CVE-2024-50571: Heap Overflow in fgfmsd

Published Oct 14, 2025
·
Updated

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.

Other sources

A heap-based buffer overflow vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7.6.2, FortiAnalyzer 7.4.0 through 7.4.5, FortiAnalyzer 7.2.0 through 7.2.9, FortiAnalyzer 7.0.0 through 7.0.13, FortiAnalyzer 6.4 all versions, FortiAnalyzer 6.2 all versions, FortiAnalyzer 6.0 all versions, FortiAnalyzer Cloud 7.4.1 through 7.4.5, FortiAnalyzer Cloud 7.2.1 through 7.2.9, FortiAnalyzer Cloud 7.0.1 through 7.0.13, FortiAnalyzer Cloud 6.4 all versions, FortiManager 7.6.0 through 7.6.1, FortiManager 7.4.0 through 7.4.5, FortiManager 7.2.0 through 7.2.9, FortiManager 7.0.0 through 7.0.13, FortiManager 6.4 all versions, FortiManager 6.2 all versions, FortiManager 6.0 all versions, FortiManager Cloud 7.6.2, FortiManager Cloud 7.4.1 through 7.4.5, FortiManager Cloud 7.2.1 through 7.2.9, FortiManager Cloud 7.0.1 through 7.0.13, FortiManager Cloud 6.4 all versions, FortiOS 7.6.0 through 7.6.2, FortiOS 7.4.0 through 7.4.6, FortiOS 7.2.0 through 7.2.10, FortiOS 7.0.0 through 7.0.16, FortiOS 6.4.0 through 6.4.15, FortiOS 6.2 all versions, FortiProxy 7.6.0 through 7.6.1, FortiProxy 7.4.0 through 7.4.7, FortiProxy 7.2.0 through 7.2.12, FortiProxy 7.0.0 through 7.0.19, 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 allows attacker to execute unauthorized code or commands via specifically crafted requests.

— MITRE

Affected Software

67 affected componentsFixes available
Fortinet FortiOS>=7.6.0<=7.6.1, >=7.4.0<=7.4.5, >=7.2.0<=7.2.10, >=7.0.0<=7.0.16, >=6.4.0<=6.4.15, >=6.2.0<=6.2.17
Fortinet FortiManager Cloud>=7.4.1<=7.4.5, >=7.2.1<=7.2.8, >=7.0.1<=7.0.13, >=6.4.1<=6.4.7
Fortinet FortiAnalyzer Cloud>=7.4.1<=7.4.5, >=7.2.1<=7.2.8, >=7.0.1<=7.0.13, >=6.4.1<=6.4.7
Fortinet FortiProxy>=7.4.0<=7.4.6, >=7.2.0<=7.2.12, >=7.0.0<=7.0.19, >=2.0.0<=2.0.14, >=1.2.0<=1.2.13, >=1.1.0<=1.1.6, >=1.0.0<=1.0.7
Fortinet FortiAnalyzer>=7.6.0<=7.6.2, >=7.4.0<=7.4.5, >=7.2.0<=7.2.8, >=7.0.0<=7.0.13, >=6.4.0<=6.4.15, >=6.2.0<=6.2.13, >=6.0.0<=6.0.12
Fortinet FortiManager>=7.6.0<=7.6.1, >=7.4.0<=7.4.5, >=7.2.0<=7.2.9, >=7.0.0<=7.0.13, >=6.4.0<=6.4.15, >=6.2.0<=6.2.13, >=6.0.0<=6.0.12
Fortinet FortiAnalyzer>=7.6.0<=7.6.2
Fortinet FortiAnalyzer>=7.4.0<=7.4.5
Fortinet FortiAnalyzer>=7.2.0<=7.2.9
Fortinet FortiAnalyzer>=7.0.0<=7.0.13
Fortinet FortiAnalyzer>=6.4
Fortinet FortiAnalyzer>=6.2
Fortinet FortiAnalyzer>=6.0
Fortinet FortiAnalyzer Cloud>=7.4.1<=7.4.5
Fortinet FortiAnalyzer Cloud>=7.2.1<=7.2.9
Fortinet FortiAnalyzer Cloud>=7.0.1<=7.0.13
Fortinet FortiAnalyzer Cloud>=6.4
Fortinet FortiManager>=7.6.0<=7.6.1
Fortinet FortiManager>=7.4.0<=7.4.5
Fortinet FortiManager>=7.2.0<=7.2.9
Fortinet FortiManager>=7.0.0<=7.0.13
Fortinet FortiManager>=6.4
Fortinet FortiManager>=6.2
Fortinet FortiManager>=6.0
Fortinet FortiManager Cloud=.
Fortinet FortiManager Cloud>=7.4.1<=7.4.5
Fortinet FortiManager Cloud>=7.2.1<=7.2.9
Fortinet FortiManager Cloud>=7.0.1<=7.0.13
Fortinet FortiManager Cloud>=6.4
Fortinet FortiOS>=7.6.0<=7.6.1
Fortinet FortiOS>=7.4.0<=7.4.6
Fortinet FortiOS>=7.2.0<=7.2.10
Fortinet FortiOS>=7.0.0<=7.0.16
Fortinet FortiOS>=6.4.0<=6.4.15
Fortinet FortiOS>=6.2
Fortinet FortiProxy=.
Fortinet FortiProxy>=7.4.0<=7.4.7
Fortinet FortiProxy>=7.2.0<=7.2.12
Fortinet FortiProxy>=7.0.0<=7.0.19
Fortinet FortiProxy>=2.0
Fortinet FortiProxy>=1.2
Fortinet FortiProxy>=1.1
Fortinet FortiProxy>=1.0
Fortinet FortiAnalyzer>=7.0.0<7.0.14
Fortinet FortiAnalyzer>=7.2.0<7.2.10
Fortinet FortiAnalyzer>=7.4.0<7.4.6
Fortinet FortiAnalyzer>=7.6.0<7.6.3
Fortinet FortiAnalyzer Cloud>=6.4.1<7.0.14
Fortinet FortiAnalyzer Cloud>=7.2.1<7.2.10
Fortinet FortiAnalyzer Cloud>=7.4.1<7.4.6
Fortinet FortiManager>=6.0.0<7.0.14
Fortinet FortiManager>=7.2.0<7.2.10
Fortinet FortiManager>=7.4.0<7.4.6
Fortinet FortiManager>=7.6.0<7.6.2
Fortinet FortiManager Cloud>=6.4.1<7.0.14
Fortinet FortiManager Cloud>=7.2.1<7.2.10
Fortinet FortiManager Cloud>=7.4.1<7.4.6
Fortinet FortiManager Cloud=7.6.2
Fortinet FortiOS>=6.2.0<6.4.16
Fortinet FortiOS>=7.0.0<7.0.17
Fortinet FortiOS>=7.2.0<7.2.11
Fortinet FortiOS>=7.4.0<7.4.7
Fortinet FortiOS>=7.6.0<7.6.3
Fortinet FortiProxy>=1.0.0<7.0.20
Fortinet FortiProxy>=7.2.0<7.2.13
Fortinet FortiProxy>=7.4.0<7.4.8
Fortinet FortiProxy=7.6.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade FortiAnalyzer Cloud to a version that resolves this vulnerability.

    Fixed in 7.0.14
  2. Upgrade

    Upgrade FortiAnalyzer Cloud to a version that resolves this vulnerability.

    Fixed in 7.2.10
  3. Upgrade

    Upgrade FortiAnalyzer Cloud to a version that resolves this vulnerability.

    Fixed in 7.4.6
  4. Upgrade

    Upgrade FortiAnalyzer Cloud to a version that resolves this vulnerability.

    Fixed in 7.6.2
  5. Upgrade

    Upgrade FortiAnalyzer to a version that resolves this vulnerability.

    Fixed in 7.0.14
  6. Upgrade

    Upgrade FortiAnalyzer to a version that resolves this vulnerability.

    Fixed in 7.2.10
  7. Upgrade

    Upgrade FortiAnalyzer to a version that resolves this vulnerability.

    Fixed in 7.4.6
  8. Upgrade

    Upgrade FortiAnalyzer to a version that resolves this vulnerability.

    Fixed in 7.6.3
  9. Upgrade

    Upgrade FortiManager Cloud to a version that resolves this vulnerability.

    Fixed in 7.0.14
  10. Upgrade

    Upgrade FortiManager Cloud to a version that resolves this vulnerability.

    Fixed in 7.2.10
  11. Upgrade

    Upgrade FortiManager Cloud to a version that resolves this vulnerability.

    Fixed in 7.4.6
  12. Upgrade

    Upgrade FortiManager Cloud to a version that resolves this vulnerability.

    Fixed in 7.6.3
  13. Upgrade

    Upgrade FortiManager to a version that resolves this vulnerability.

    Fixed in 7.0.14
  14. Upgrade

    Upgrade FortiManager to a version that resolves this vulnerability.

    Fixed in 7.2.10
  15. Upgrade

    Upgrade FortiManager to a version that resolves this vulnerability.

    Fixed in 7.4.6
  16. Upgrade

    Upgrade FortiManager to a version that resolves this vulnerability.

    Fixed in 7.6.2
  17. Upgrade

    Upgrade FortiOS to a version that resolves this vulnerability.

    Fixed in 6.4.16
  18. Upgrade

    Upgrade FortiOS to a version that resolves this vulnerability.

    Fixed in 7.0.17
  19. Upgrade

    Upgrade FortiOS to a version that resolves this vulnerability.

    Fixed in 7.2.11
  20. Upgrade

    Upgrade FortiOS to a version that resolves this vulnerability.

    Fixed in 7.4.7
  21. Upgrade

    Upgrade FortiOS to a version that resolves this vulnerability.

    Fixed in 7.6.3
  22. Upgrade

    Upgrade FortiProxy to a version that resolves this vulnerability.

    Fixed in 7.0.20
  23. Upgrade

    Upgrade FortiProxy to a version that resolves this vulnerability.

    Fixed in 7.2.13
  24. Upgrade

    Upgrade FortiProxy to a version that resolves this vulnerability.

    Fixed in 7.4.8
  25. Upgrade

    Upgrade FortiProxy to a version that resolves this vulnerability.

    Fixed in 7.6.2

Event History

Oct 14, 2025
Advisory Published
via FortiGuard·12:00 AM
Data Sourced
via FortiGuard·12:00 AM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·03:23 PM
Data Sourced
via MITRE·03:23 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-50571?

CVE-2024-50571 is classified as a critical vulnerability due to its potential to cause a heap-based buffer overflow.

2

How do I fix CVE-2024-50571?

To remediate CVE-2024-50571, upgrade your Fortinet FortiOS to version 7.6.3 or later.

3

Which Fortinet products are affected by CVE-2024-50571?

CVE-2024-50571 affects multiple versions of FortiOS, FortiManager, and FortiAnalyzer across various releases.

4

What happens if I do not address CVE-2024-50571?

Failure to address CVE-2024-50571 could lead to exploitation, resulting in unauthorized access and control over affected systems.

5

How critical is CVE-2024-50571 for my organization?

CVE-2024-50571 poses a high risk to organizations using vulnerable versions of Fortinet products, necessitating prompt action to mitigate potential threats.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203