dbcve.org
FortiosOperating system · Fortinet

CVE-2024-23110

HIGH · 7.8 CVSS v3.1 Published 2024-06-11
Fix available
A fix is available. Upgrade to 6.2.16 / 6.4.15 or later.
See remediation →
80/100
Remediation priority · High
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 in Fortinet FortiOS version 7.4.0 through 7.4.2, 7.2.0 through 7.2.6, 7.0.0 through 7.0.13, 6.4.0 through 6.4.14, 6.2.0 through 6.2.15, 6.0 all versions allows attacker to execute unauthorized code or commands via specially crafted commands

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 allows attackers to execute unauthorized code or commands via specially crafted HTTP/HTTPS requests. The flaw exists in the handling of certain commands, where insufficient bounds checking on stack-allocated buffers permits overflowing adjacent memory and overwriting return addresses. This can lead to arbitrary code execution with elevated privileges.

MitigationApply the relevant FortiOS firmware update from Fortinet's security advisory. For affected versions (7.4.x, 7.2.x, 7.0.x, 6.4.x, 6.2.x, 6.0.x), upgrade to the patched versions as specified in the Fortinet PSIRT advisory. If immediate patching is not feasible, restrict management interface access to trusted IP addresses via firewall policies or VPN.

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:>= 6.0.0, < 6.2.16>= 6.4.0, < 6.4.15>= 7.0.0, < 7.0.14>= 7.2.0, < 7.2.7>= 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 the FortiOS version
    Run 'get system status' via CLI or check the FortiOS dashboard firmware version display. Compare the installed version against the affected ranges: 6.0.0 to 6.2.15, 6.4.0 to 6.4.14, 7.0.0 to 7.0.13, 7.2.0 to 7.2.6, and 7.4.0 to 7.4.2.
    Affected if The installed version falls within any of these ranges.
  2. Verify HTTP/HTTPS management interface exposure
    Check firewall policies and interface settings to determine if the FortiOS GUI (HTTP port 80/HTTPS port 443) or CLI management ports are reachable from untrusted networks or the internet. Review the 'system interface' configuration and 'firewall policy' settings.
    Affected if HTTP or HTTPS management access is permitted from untrusted IP addresses or external networks.
  3. Review administrative access policies
    Inspect the administrative access list under 'System > Network > Interfaces' or via 'show system interface' CLI command to list all interfaces with HTTP, HTTPS, SSH, or Telnet access enabled.
    Affected if Administrative protocols (HTTP/HTTPS) are enabled on external or untrusted-facing interfaces.
  4. Check for trusted host restrictions
    Examine the admin user configuration via 'show system admin' CLI command to verify if trusted host IP restrictions are defined for administrative accounts.
    Affected if No trusted host restrictions are configured, or the defined trusted hosts include broad/untrusted IP ranges.

You are affected if your FortiOS version is 6.0.0-6.2.15, 6.4.0-6.4.14, 7.0.0-7.0.13, 7.2.0-7.2.6, or 7.4.0-7.4.2 AND the management interface is accessible from untrusted networks.

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.16 / 6.4.15 / 7.0.14 or later
Fixed in 6.2.166.4.157.0.14
Interim mitigation

Apply the relevant FortiOS firmware update from Fortinet's security advisory. For affected versions (7.4.x, 7.2.x, 7.0.x, 6.4.x, 6.2.x, 6.0.x), upgrade to the patched versions as specified in the Fortinet PSIRT advisory. If immediate patching is not feasible, restrict management interface access to trusted IP addresses via firewall policies or VPN.

Recommended fix High confidence

Upgrade to FortiOS 6.2.16 (or 6.4.15, 7.0.14, or 7.2.7 depending on your current branch; for 7.4.x deployments upgrade to 7.4.3 or later)

  1. 1. Identify the current FortiOS version by running 'get system status' or 'fwsm -get system status' on the FortiGate CLI
  2. 2. Determine which version branch your current installation belongs to (6.0.x, 6.2.x, 6.4.x, 7.0.x, or 7.2.x)
  3. 3. For FortiOS 6.0.x/6.2.x: Upgrade to version 6.2.16 or later
  4. 4. For FortiOS 6.4.x: Upgrade to version 6.4.15 or later
  5. 5. For FortiOS 7.0.x: Upgrade to version 7.0.14 or later
  6. 6. For FortiOS 7.2.x: Upgrade to version 7.2.7 or later
  7. 7. Download the appropriate firmware from Fortinet's support portal (https://support.fortinet.com)
  8. 8. Upload and install the firmware via the FortiGate GUI (System > Firmware) or CLI using 'execute firmware upgrade'
Caveat Review Fortinet's release notes for your target version to check for configuration or feature changes that may require adjustments; major version jumps (e.g., 6.x to 7.x) may require more extensive testing

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

Fix this in Fortios 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-23110 — 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-23110 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