FortiosOperating system · Fortinet

CVE-2024-35279

HIGH · 8.1 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 7.2.9 / 7.4.5 or later.
See remediation →
90/100
Remediation priority · Urgent
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 stack-based buffer overflow [CWE-121] vulnerability in Fortinet FortiOS version 7.2.4 through 7.2.8 and version 7.4.0 through 7.4.4 allows a remote unauthenticated attacker to execute arbitrary code or commands via crafted UDP packets through the CAPWAP control, provided the attacker were able to evade FortiOS stack protections and provided the fabric service is running on the exposed interface.

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

A stack-based buffer overflow vulnerability in FortiOS versions 7.2.4-7.2.8 and 7.4.0-7.4.4 allows remote unauthenticated attackers to execute arbitrary code via crafted UDP packets through the CAPWAP control protocol, provided the fabric service is running on the exposed interface and stack protection mechanisms can be evaded.

MitigationUpgrade FortiOS to the latest patched version beyond 7.2.8 and 7.4.4, and disable the fabric service on externally-facing interfaces if not required, as exploitation requires the service to be accessible on the target interface.

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
FortiosOperating system
Affected:>= 7.2.4, < 7.2.9>= 7.4.0, < 7.4.5

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/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 FortiOS version
    Run 'get system status' or 'diag sys flash list' from CLI to retrieve the installed FortiOS version.
    Affected if The installed version falls within 7.2.4-7.2.8 or 7.4.0-7.4.4 ranges.
  2. Verify fabric service status
    Run 'get system interface' and inspect the 'fabric' status for each interface, or check via GUI under Network > Interfaces to see if the fabric service is enabled on any interface.
    Affected if The fabric service is enabled on an interface reachable by untrusted networks (such as external/WAN-facing interfaces).

You are affected if your FortiOS version is 7.2.4 through 7.2.8 or 7.4.0 through 7.4.4 AND the fabric service is running on a network interface accessible to unauthenticated 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 7.2.9 / 7.4.5 or later
Fixed in 7.2.97.4.5
Interim mitigation

Upgrade FortiOS to the latest patched version beyond 7.2.8 and 7.4.4, and disable the fabric service on externally-facing interfaces if not required, as exploitation requires the service to be accessible on the target interface.

Recommended fix High confidence

FortiOS 7.2.9 or 7.4.5 (or later stable releases within the same major branch)

  1. 1. Identify the current FortiOS version using 'get system status' or through the FortiOS GUI under Dashboard > Status
  2. 2. For FortiOS 7.2.x deployments: Plan upgrade to version 7.2.9 or later
  3. 3. For FortiOS 7.4.x deployments: Plan upgrade to version 7.4.5 or later
  4. 4. Before upgrading, review Fortinet release notes for the target version for any migration considerations
  5. 5. Perform a backup of the current FortiOS configuration
  6. 6. Download the firmware from Fortinet Customer Support portal or FortiGuard
  7. 7. Upload and install the firmware via FortiOS GUI (System > Firmware) or CLI: 'execute firmware upgrade <image>'
  8. 8. After reboot, verify the upgrade was successful with 'get system status' and confirm the version number
Caveat Minor version upgrades typically preserve configuration; always review release notes for behavioral changes before upgrading

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

Fix this in Fortios Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-35279 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