dbcve.org
FortiosOperating system · Fortinet

CVE-2024-46670

HIGH · 7.5 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 7.2.10 / 7.4.5 or later.
See remediation →
84/100
Remediation priority · High
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
An Out-of-bounds Read vulnerability [CWE-125] in FortiOS version 7.6.0, version 7.4.4 and below, version 7.2.9 and below and FortiSASE FortiOS tenant version 24.3.b IPsec IKE service may allow an unauthenticated remote attacker to trigger memory consumption leading to Denial of Service via 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

An out-of-bounds read vulnerability (CWE-125) in FortiOS IPsec IKE service allows unauthenticated remote attackers to trigger excessive memory consumption via crafted IKE requests, leading to denial of service. The vulnerability affects FortiOS 7.6.0, 7.4.4 and below, 7.2.9 and below, and FortiSASE FortiOS tenant version 24.3.b.

MitigationUpgrade FortiOS to version 7.4.5 or above, 7.2.10 or above, 7.6.1 or above, or FortiSASE tenant version 24.3.c or later to patch the vulnerability. If immediate upgrade is not possible, consider restricting IKE service exposure to untrusted networks via firewall policies.

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.0, < 7.2.10>= 7.4.0, < 7.4.5= 7.6.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the command 'get system status' on the FortiGate CLI or check the firmware version in the web UI under Dashboard > Status. Look for the Firmware Version field.
    Affected if Version is 7.2.0 through 7.2.9, 7.4.0 through 7.4.4, or exactly 7.6.0, or FortiSASE tenant version 24.3.b.
  2. Verify IPsec IKE service is enabled
    Run 'diagnose vpn ike status' in the CLI to list active IKE gateways and their status. Alternatively, check the IPsec VPN configuration in the web UI under VPN > IPsec Wizard or 'config vpn ipsec phase1-interface' in CLI.
    Affected if Any IPsec phase1 interface is configured and the IKE service is active (showing as 'up' or 'listen').
  3. Check IKE service listening status
    Run 'diagnose system service dump' or 'diagnose hardware deviceinfo nic' to verify UDP ports 500 and 4500 are open and listening for IKE traffic.
    Affected if The IKE service is bound to UDP 500/4500 and accepting connections.
  4. Assess network exposure of IKE ports
    Review firewall policy source addresses and interface settings for any policies allowing IKE traffic from untrusted external networks. Run 'diagnose firewall policy list' and filter for IKE-related policies with 'any' or external WAN interfaces as sources.
    Affected if IKE service is reachable from untrusted networks (WAN interfaces, 'any' source address, or no source address restriction).

You are affected if FortiOS version is 7.2.0-7.2.9, 7.4.0-7.4.4, or 7.6.0 (or FortiSASE 24.3.b) AND IPsec IKE is enabled and exposed to 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 7.2.10 / 7.4.5 or later
Fixed in 7.2.107.4.5
Interim mitigation

Upgrade FortiOS to version 7.4.5 or above, 7.2.10 or above, 7.6.1 or above, or FortiSASE tenant version 24.3.c or later to patch the vulnerability. If immediate upgrade is not possible, consider restricting IKE service exposure to untrusted networks via firewall policies.

Recommended fix High confidence

FortiOS 7.2.10+ (for 7.2.x branch), FortiOS 7.4.5+ (for 7.4.x branch), or FortiOS 7.6.1+ (for 7.6.0 branch)

  1. 1. Identify the current FortiOS version running on the device using 'get system status' or 'FW: # get version' command
  2. 2. Determine which upgrade path applies based on current version branch (7.2.x, 7.4.x, or 7.6.0)
  3. 3. Download the appropriate fixed firmware image from Fortinet customer support portal or FortiGuard
  4. 4. Upload the firmware to the FortiOS device via Web UI (System > Firmware) or CLI: 'execute firmware upload <image>'
  5. 5. Backup current configuration using 'execute backup config' command
  6. 6. Initiate firmware upgrade: For CLI, use 'execute system firmware-upgrade <image> tftp|ftp|usb' or use Web UI firmware upgrade feature
  7. 7. Confirm the upgrade completes and system reboots successfully
  8. 8. Verify the new version is running: 'get system status' and confirm version is >= 7.2.10, >= 7.4.5, or > 7.6.0
Caveat Review Fortinet release notes for the target version for any configuration or feature changes before upgrading; test in non-production environment first

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

Fix this in Fortios Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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