dbcve.org
FortiproxyApplication · Fortinet

CVE-2024-50568

MEDIUM · 5.9 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 7.0.17 / 7.2.9 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 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 channel accessible by non-endpoint vulnerability [CWE-300] in Fortinet FortiOS version 7.4.0 through 7.4.3, 7.2.0 through 7.2.7 and before 7.0.14 & FortiProxy version 7.4.0 through 7.4.3, 7.2.0 through 7.2.9 and before 7.0.16 allows an unauthenticated attacker with the knowledge of device specific data to spoof the identity of a downstream device of the security fabric via crafted TCP 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

FortiOS and FortiProxy contain a channel accessible by non-endpoint vulnerability (CWE-300) that allows an unauthenticated attacker with knowledge of device-specific data to spoof the identity of downstream devices in the Fortinet Security Fabric via crafted TCP requests. The vulnerability exists due to insufficient validation of device identity in the security fabric communication channel.

MitigationUpgrade FortiOS to version 7.4.4, 7.2.8, or 7.0.14 or later; upgrade FortiProxy to version 7.4.4, 7.2.10, or 7.0.16 or later. Restrict network access to management interfaces and monitor for anomalous TCP traffic targeting security fabric ports.

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
FortiproxyApplication
Affected:>= 7.0.0, < 7.0.17>= 7.2.0, < 7.2.10>= 7.4.0, < 7.4.4
FortiosOperating system
Affected:>= 6.4.2, < 7.2.9>= 7.4.0, < 7.4.4

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
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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 your FortiOS or FortiProxy version
    Run 'get system status' via CLI or check the web UI dashboard for the firmware version
    Affected if The version falls within these ranges: FortiOS >= 6.4.2 and < 7.2.9, or >= 7.4.0 and < 7.4.4; FortiProxy >= 7.0.0 and < 7.0.17, or >= 7.2.0 and < 7.2.10, or >= 7.4.0 and < 7.4.4
  2. Verify if Security Fabric is enabled
    Run 'get system status' or 'show system security-fabric' in CLI to check if Security Fabric is configured and operational
    Affected if Security Fabric is enabled and the device is acting as a Fabric root or downstream device
  3. Confirm network exposure of management and Fabric ports
    Check interface configuration with 'get system interface' and review firewall policies for port 8010 (Security Fabric communication) and management ports (HTTP/HTTPS/SSH) accessible from untrusted networks
    Affected if Management interfaces or Security Fabric ports are reachable from untrusted or external networks
  4. Review Security Fabric device topology
    Run 'execute fabric device list' to see registered downstream devices and verify which devices are communicating on the Fabric channel
    Affected if Multiple downstream devices are registered and actively communicating via the Fabric channel

You are affected if your FortiOS/FortiProxy version is within the affected ranges AND Security Fabric is enabled AND management/Fabric ports are network-accessible, allowing an unauthenticated attacker to spoof device identity in Fabric communications.

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.0.17 / 7.2.9 / 7.2.10 or later
Fixed in 7.0.177.2.97.2.10
Interim mitigation

Upgrade FortiOS to version 7.4.4, 7.2.8, or 7.0.14 or later; upgrade FortiProxy to version 7.4.4, 7.2.10, or 7.0.16 or later. Restrict network access to management interfaces and monitor for anomalous TCP traffic targeting security fabric ports.

Recommended fix High confidence

FortiOS: 7.4.4+ or 7.2.9+ or 7.0.14+ | FortiProxy: 7.4.4+ or 7.2.10+ or 7.0.17+

  1. 1. Identify the currently installed FortiOS or FortiProxy version using the CLI command: get system status
  2. 2. For FortiOS devices: Upgrade to version 7.4.4 or later, or 7.2.9 or later, or 7.0.14 or later
  3. 3. For FortiProxy devices: Upgrade to version 7.4.4 or later, or 7.2.10 or later, or 7.0.17 or later
  4. 4. Download the firmware from Fortinet's support portal: https://support.fortinet.com/
  5. 5. Upload and install the firmware via the FortiOS/FortiProxy GUI or CLI: execute system firmware upgrade <firmware_file>
  6. 6. After upgrade, verify the new version is installed: get system status
  7. 7. Test that Security Fabric functionality works correctly after the upgrade
Caveat Review Fortinet release notes for the target version to check for any configuration or feature changes that may affect your deployment

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

Fix this in Fortiproxy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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