dbcve.org
FortiwebApplication · Fortinet

CVE-2024-50565

HIGH · 7.5 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 6.2.14 / 6.4.9 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 restriction of communication channel to intended endpoints vulnerability [CWE-923] in Fortinet FortiOS version 7.4.0 through 7.4.3, 7.2.0 through 7.2.7, 7.0.0 through 7.0.14, 6.4.0 through 6.4.15 and 6.2.0 through 6.2.16, Fortinet FortiProxy version 7.4.0 through 7.4.2, 7.2.0 through 7.2.9, 7.0.0 through 7.0.15 and 2.0.0 through 2.0.14, Fortinet FortiManager version 7.4.0 through 7.4.2, 7.2.0 through 7.2.4, 7.0.0 through 7.0.11, 6.4.0 through 6.4.14 and 6.2.0 through 6.2.13, Fortinet FortiAnalyzer version 7.4.0 through 7.4.2, 7.2.0 through 7.2.4, 7.0.0 through 7.0.11, 6.4.0 through 6.4.14 and 6.2.0 through 6.2.13, Fortinet FortiVoice version 7.0.0 through 7.0.2, 6.4.0 through 6.4.8 and 6.0.0 through 6.0.12 and Fortinet FortiWeb version 7.4.0 through 7.4.2, 7.2.0 through 7.2.10, 7.0.0 through 7.0.10 allows an unauthenticated attacker in a man-in-the-middle position to impersonate the management device (FortiCloud server or/and in certain conditions, FortiManager), via intercepting the FGFM authentication request between the management device and the managed device

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

This is a man-in-the-middle vulnerability in the FGFM (FortiGate Firewall Management) protocol used by Fortinet products. An unauthenticated attacker positioned on the network can intercept the FGFM authentication request between managed devices (FortiOS, FortiProxy, FortiWeb, etc.) and management devices (FortiCloud/FortiManager), allowing impersonation of the management server. This enables the attacker to potentially inject commands or gain unauthorized control over managed devices.

MitigationApply the vendor-supplied patches for the specific Fortinet product versions. Additionally, protect management interfaces by using VPN tunnels or network segmentation to prevent MITM positioning, and ensure strong PKI/certificate validation is enforced for management communications.

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
FortiwebApplication
Affected:>= 7.4.0, < 7.4.3
FortivoiceApplication
Affected:>= 6.0.0, < 6.4.9>= 7.0.0, < 7.0.3
FortiproxyApplication
Affected:>= 2.0.0, < 7.0.16>= 7.2.0, < 7.2.10>= 7.4.0, < 7.4.3
FortiosOperating system
Affected:>= 6.4.0, < 7.0.16>= 7.2.0, < 7.2.9>= 7.4.0, < 7.4.5
FortimanagerApplication
Affected:>= 6.2.0, < 6.2.14>= 6.4.0, < 6.4.15>= 7.0.0, < 7.0.12>= 7.2.0, < 7.2.5>= 7.4.0, < 7.4.3
FortianalyzerApplication
Affected:>= 6.2.0, < 6.2.14>= 6.4.0, < 6.4.15>= 7.0.0, < 7.0.12>= 7.2.0, < 7.2.5>= 7.4.0, < 7.4.3

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 the Fortinet product and version
    Run `get system status` on the device CLI to display the product name, version, and build number
    Affected if The displayed version falls within any of the affected version ranges listed for this CVE
  2. Confirm FGFM management is configured
    Run `get system fortimanager` or `get system central-management` to check if FortiManager or FortiCloud management is enabled and configured
    Affected if FGFM-based central management is actively configured pointing to FortiManager or FortiCloud
  3. Verify management interface exposure
    Check the interface binding for FGFM: run `show system fortimanager` or `show system central-management` to see which interface(s) the management traffic uses, then verify if those interfaces are bound to external or untrusted networks
    Affected if The management interface is bound to a WAN-facing or otherwise untrusted network segment where an attacker could position themselves
  4. Check for PKI/certificate validation settings
    Run `show system fortimanager` and look for certificate-validation settings or run `diagnose fortimanager ssl-certificate verify` to see if certificate validation is enforced
    Affected if Certificate validation is disabled or set to optional for FGFM communications

You are affected if your device runs a Fortinet product version within the listed ranges AND has FGFM-based central management (FortiCloud/FortiManager) enabled on an interface accessible to potential MITM attackers.

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 6.2.14 / 6.4.9 / 6.4.15 or later
Fixed in 6.2.146.4.96.4.15
Interim mitigation

Apply the vendor-supplied patches for the specific Fortinet product versions. Additionally, protect management interfaces by using VPN tunnels or network segmentation to prevent MITM positioning, and ensure strong PKI/certificate validation is enforced for management communications.

Recommended fix High confidence

Upgrade to the latest stable FortiOS/FortiProxy/FortiManager/FortiAnalyzer/FortiVoice/FortiWeb release in each respective version branch

  1. 1. Identify the affected Fortinet product (FortiOS, FortiProxy, FortiManager, FortiAnalyzer, FortiVoice, or FortiWeb) in your environment
  2. 2. Determine the current installed version of the affected product
  3. 3. For FortiOS: upgrade to 7.4.5 or later, 7.2.9 or later, or 7.0.16 or later
  4. 4. For FortiProxy: upgrade to 7.4.3 or later, 7.2.10 or later, or 7.0.16 or later
  5. 5. For FortiManager: upgrade to 7.2.5 or later, 7.0.12 or later, 6.4.15 or later, or 6.2.14 or later
  6. 6. For FortiAnalyzer: upgrade to 7.2.5 or later, 7.0.12 or later, 6.4.15 or later, or 6.2.14 or later
  7. 7. For FortiVoice: upgrade to 7.0.3 or later, 6.4.9 or later, or 6.0.13 or later
  8. 8. For FortiWeb: upgrade to 7.4.3 or later, 7.2.11 or later, or 7.0.11 or later

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

Fix this in Fortiweb Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-50565 — 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-50565 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