dbcve.org
FortiosOperating system · Fortinet

CVE-2024-46666

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 7.2.9 / 7.4.5 or later.
See remediation →
62/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
An allocation of resources without limits or throttling [CWE-770] vulnerability in FortiOS versions 7.6.0, versions 7.4.4 through 7.4.0, 7.2 all versions, 7.0 all versions, 6.4 all versions may allow a remote unauthenticated attacker to prevent access to the GUI via specially crafted requests directed at specific endpoints.

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

A resource exhaustion vulnerability in FortiOS allows remote unauthenticated attackers to send specially crafted requests to specific GUI endpoints, causing excessive resource allocation that prevents GUI access. This is a denial-of-service condition affecting the web-based management interface.

MitigationApply Fortinet's patch for this vulnerability when available, and consider implementing upstream rate limiting or access controls to limit exposure to the GUI interface from untrusted networks.

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.4.0, < 7.2.9>= 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
Low

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

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 installed FortiOS version
    Run the command 'get system status' or 'fortios -v' via CLI to retrieve the firmware version. Alternatively, log into the GUI and check System > Firmware & General > FortiGuard for the current version.
    Affected if The version number falls within 6.4.0 to 7.2.8, 7.4.0 to 7.4.4, or equals 7.6.0.
  2. Confirm GUI interface is enabled and accessible
    Run 'get system interface | grep -A 5 mgmt' or check System > Network > Interfaces in the GUI to verify the management interface has 'HTTPS' service enabled and is bound to a reachable network.
    Affected if The GUI (HTTPS service) is enabled on any interface that is reachable from untrusted networks.
  3. Check external access exposure to GUI
    Review the interface binding configuration via 'show system interface' CLI command or System > Network > Interfaces in the GUI. Look for 'set allowaccess https' on interfaces with external IP addresses or in untrusted zones.
    Affected if The management interface with HTTPS enabled is assigned to a zone or IP range accessible from the internet or untrusted internal networks.
  4. Inspect existing rate limiting configuration
    Run 'get firewall profile6' or check Policy & Objects > Traffic Shapers to see if any rate-limiting or connection-filters are applied to management traffic.
    Affected if No rate limiting is configured for GUI management traffic, leaving the interface vulnerable to excessive request attacks.

You are affected if your FortiOS version falls within the listed vulnerable ranges AND the GUI management interface is exposed and reachable from networks where untrusted attackers could send requests.

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

Apply Fortinet's patch for this vulnerability when available, and consider implementing upstream rate limiting or access controls to limit exposure to the GUI interface from untrusted networks.

Recommended fix High confidence

FortiOS 7.2.9+ (for 6.4.x/7.0.x/7.2.x) or FortiOS 7.4.5+ (for 7.4.x) or FortiOS 7.6.1+ (for 7.6.0)

  1. Identify current FortiOS version using 'get system status' or through the GUI dashboard
  2. For FortiOS 6.4.x: Schedule maintenance window and upgrade to version 7.2.9 or later (recommended: 7.2.x latest)
  3. For FortiOS 7.0.x: Schedule maintenance window and upgrade to version 7.2.9 or later (recommended: 7.2.x latest)
  4. For FortiOS 7.2.x: Schedule maintenance window and upgrade to version 7.2.9 or later (recommended: 7.2.x latest)
  5. For FortiOS 7.4.0-7.4.4: Schedule maintenance window and upgrade to version 7.4.5 or later (recommended: 7.4.x latest)
  6. For FortiOS 7.6.0: Upgrade to version 7.6.1 or later when available
  7. Upload new firmware via FortiOS GUI (System > Firmware) or CLI: 'execute upgrade'
  8. Verify upgrade success and confirm GUI accessibility
Caveat Review FortiOS release notes for potential configuration or feature changes between major versions; test upgrade in staging environment before production deployment

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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