dbcve.org
FortiosOperating system · Fortinet

CVE-2024-46669

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 7.4.5 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Integer Overflow or Wraparound vulnerability [CWE-190] in version 7.4.4 and below, version 7.2.10 and below; FortiSASE version 23.4.b FortiOS tenant IPsec IKE service may allow an authenticated attacker to crash the IPsec tunnel via crafted requests, resulting in potential denial of service.

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 · moderate confidence

An integer overflow vulnerability (CWE-190) exists in the IPsec IKE service of FortiOS 7.4.4 and below, 7.2.10 and below, and FortiSASE 23.4.b. An authenticated attacker can send crafted requests to trigger the overflow, causing the IPsec tunnel to crash and resulting in denial of service.

MitigationUpgrade FortiOS to version 7.4.5 or higher (for the 7.4 branch) or 7.2.11 or higher (for the 7.2 branch), and FortiSASE to a patched version beyond 23.4.b.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Check FortiOS version
    Run `get system status` on the FortiGate CLI or check the web UI under Dashboard > Status. Look for the Firmware Version field.
    Affected if The displayed version is 7.2.0 through 7.2.10, or 7.4.0 through 7.4.4 (versions below 7.4.5 in the 7.4 branch, or below 7.2.11 in the 7.2 branch).
  2. Verify IPsec VPN is configured
    Run `get vpn ipsec phase2` or `diagnose vpn ike status` in the CLI to list active IPsec phase2 configurations.
    Affected if Any IPsec tunnels (phase2 entries) are configured and active, as the vulnerability exists in the IKE service handling these tunnels.
  3. Confirm IKE daemon is running
    Run `diagnose sys process list | grep -i ike` or `diagnose vpn ike gateway list` to verify the IKE process is active.
    Affected if The IKE daemon is running, which is required for the integer overflow to be triggerable.
  4. Check for remote authentication access
    Run `get system admin` or review the admin user configuration to determine if remote authentication (RADIUS, LDAP, or local users) is enabled that would allow an authenticated attacker to connect.
    Affected if Remote administrative access or user VPN authentication is enabled, providing a path for an authenticated attacker to send crafted requests.

You are affected if your FortiOS version is 7.2.0-7.2.10 or 7.4.0-7.4.4 AND IPsec IKE is configured with an authenticated user able to access the VPN or admin interface.

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.4.5 or later
Fixed in 7.4.5
Interim mitigation

Upgrade FortiOS to version 7.4.5 or higher (for the 7.4 branch) or 7.2.11 or higher (for the 7.2 branch), and FortiSASE to a patched version beyond 23.4.b.

Recommended fix High confidence

FortiOS 7.4.5 or later (or FortiOS 7.2.11+ for 7.2.x branch)

  1. Backup current FortiOS configuration using 'execute backup config' or through the web UI
  2. Download the firmware upgrade from Fortinet support portal - target version 7.4.5 or later (or 7.2.11+ for 7.2.x branch)
  3. Upload the firmware file via web UI (System > Firmware) or CLI: 'execute firmware upload'
  4. Reboot the FortiGate device to apply the new firmware
  5. After reboot, verify the firmware version with 'get system status' and confirm the IPsec IKE service is operational
  6. Test IPsec tunnel establishment to confirm the fix resolves the integer overflow vulnerability
Caveat Review FortiOS 7.4.5 release notes for any configuration or feature changes; minor version upgrades within the same branch typically have low risk

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

Fix this in Fortios Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,950
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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