dbcve.org
FortimanagerApplication · Fortinet

CVE-2024-50566

HIGH · 8.8 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 7.2.8 / 7.2.9 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet FortiManager Cloud 7.6.0 through 7.6.1, FortiManager Cloud 7.4.0 through 7.4.4, FortiManager Cloud 7.2.2 through 7.2.7, FortiManager 7.6.0 through 7.6.1, FortiManager 7.4.0 through 7.4.5, FortiManager 7.2.1 through 7.2.8 may allow an authenticated remote attacker to execute unauthorized code via FGFM crafted requests.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OS command injection vulnerability in FortiManager's FGFM (FortiManager Flash File Management) protocol allows authenticated remote attackers to execute unauthorized code via specially crafted FGFM requests. The vulnerability affects both FortiManager Cloud and on-premise versions across multiple release branches (7.2.x, 7.4.x, 7.6.x).

MitigationApply vendor-supplied patches or upgrade to FortiManager versions 7.2.9+, 7.4.6+, or 7.6.2+ as appropriate. Additionally, restrict FGFM access to trusted networks and enforce strict authentication controls to limit attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FortimanagerApplication
Affected:>= 7.2.1, < 7.2.9>= 7.4.0, < 7.4.6>= 7.6.0, < 7.6.2
Fortimanager CloudApplication
Affected:>= 7.2.2, < 7.2.8>= 7.4.0, < 7.4.5>= 7.6.0, < 7.6.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify FortiManager version
    Run `get system status` in FortiManager CLI or check System > FortiGuard in web UI
    Affected if The displayed version falls within 7.2.1-7.2.8, 7.4.0-7.4.5, or 7.6.0-7.6.1 for on-premise; or 7.2.2-7.2.7, 7.4.0-7.4.4, or 7.6.0-7.6.1 for Cloud versions
  2. Confirm FGFM protocol is enabled
    Run `get system global | grep fgfm` in FortiManager CLI to check FGFM daemon status
    Affected if FGFM is enabled (fgfm-sock-timeout is set to a non-zero value or fgfm-port is configured)
  3. Check FGFM service listening status
    Run `diagnose test application fgfm 1` in FortiManager CLI to verify FGFM daemon is running
    Affected if FGFM daemon shows as running and listening on port 541
  4. Determine FGFM network exposure
    Run `show system interface` and check firewall policies for port 541 (default FGFM port) accessibility from untrusted networks
    Affected if FGFM port 541 is exposed to internet or untrusted networks without adequate access controls
  5. Verify remote authentication configuration
    Run `get system admin` in CLI and check if remote RADIUS or LDAP authentication is enabled for admin accounts
    Affected if Remote authentication is configured and enabled for administrative access

You are affected if your FortiManager version is within the vulnerable ranges AND FGFM protocol is enabled and accessible to the attacker.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.2.8 / 7.2.9 / 7.4.5 or later
Fixed in 7.2.87.2.97.4.5
Interim mitigation

Apply vendor-supplied patches or upgrade to FortiManager versions 7.2.9+, 7.4.6+, or 7.6.2+ as appropriate. Additionally, restrict FGFM access to trusted networks and enforce strict authentication controls to limit attack surface.

Recommended fix High confidence

FortiManager: 7.2.9, 7.4.6, or 7.6.2 | FortiManager Cloud: 7.2.8, 7.4.5, or 7.6.2

  1. 1. Identify the current FortiManager or FortiManager Cloud version by navigating to System Settings > FortiManager or using 'get system status' CLI command
  2. 2. Based on the current version branch, plan upgrade to the fixed release: For 7.2.x branch, upgrade to 7.2.9 or later; For 7.4.x branch, upgrade to 7.4.6 or later; For 7.6.x branch, upgrade to 7.6.2 or later
  3. 3. Backup the FortiManager configuration using the GUI (System Settings > Maintenance > Backup) or CLI command 'execute backup full-config', or use FortiManager's snapshot feature for cloud instances
  4. 4. For FortiManager (hardware/VM), review the FortiManager Upgrade Path documentation to ensure no intermediate upgrades are needed between current version and target fixed version
  5. 5. For FortiManager Cloud, contact Fortinet support or use the cloud console's upgrade mechanism to upgrade to the fixed version
  6. 6. After upgrade, verify the version using 'get system status' and confirm FGFM-related functionality is working correctly
  7. 7. Validate that the vulnerability is addressed by reviewing the FortiManager release notes for the fixed version
Caveat Major version upgrades may require configuration adjustments; review FortiManager release notes for any breaking changes between versions. Test in non-production environment first.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortimanager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-50566 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-50566 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data