dbcve.org
FortianalyzerApplication · Fortinet

CVE-2024-23666

HIGH · 8.8 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 6.4.15 / 7.0.13 or later.
See remediation →
94/100
Remediation priority · Urgent
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
A client-side enforcement of server-side security in Fortinet FortiAnalyzer-BigData at least version 7.4.0 and 7.2.0 through 7.2.6 and 7.0.1 through 7.0.6 and 6.4.5 through 6.4.7 and 6.2.5, FortiManager version 7.4.0 through 7.4.1 and 7.2.0 through 7.2.4 and 7.0.0 through 7.0.11 and 6.4.0 through 6.4.14, FortiAnalyzer version 7.4.0 through 7.4.1 and 7.2.0 through 7.2.4 and 7.0.0 through 7.0.11 and 6.4.0 through 6.4.14 allows attacker to improper access control 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 · moderate confidence

This is an access control vulnerability where FortiAnalyzer-BigData, FortiManager, and FortiAnalyzer rely on client-side validation instead of enforcing proper server-side authorization checks. An attacker can exploit this by sending crafted requests that bypass the missing server-side access controls, potentially allowing unauthorized access to functionality or data that should be restricted.

MitigationApply the vendor-supplied patches from Fortinet for the affected versions. Until patches are applied, implement network segmentation and restrict administrative access to trusted IP addresses only.

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
FortianalyzerApplication
Affected:>= 6.4.0, < 6.4.15>= 7.0.0, < 7.0.13>= 7.2.0, < 7.2.6>= 7.4.0, < 7.4.3
Fortianalyzer Big DataApplication
Affected:>= 6.2.1, < 7.2.7= 7.4.0
FortimanagerApplication
Affected:>= 6.4.0, < 6.4.15>= 7.0.0, < 7.0.13>= 7.2.0, < 7.2.6>= 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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 installed Fortinet product
    Run the command 'get system status' in the FortiAnalyzer/FortiManager CLI, or check the product name in the web interface login page footer
    Affected if The product is FortiAnalyzer, FortiAnalyzer Big Data, or FortiManager
  2. Determine the firmware version
    Run 'get system status' in the CLI and locate the 'Version' field, or check the System > Firmware page in the web interface
    Affected if The displayed version falls within any of these ranges: 6.4.0-6.4.14, 7.0.0-7.0.12, 7.2.0-7.2.5, 7.4.0-7.4.2 (for FortiAnalyzer/FortiManager); 6.2.1-7.2.6 or 7.4.0 (for FortiAnalyzer Big Data)
  3. Verify admin interface accessibility
    Confirm the web-based administrative interface is reachable on the device (HTTPS on port 443 or configured admin port)
    Affected if The admin interface is exposed to network segments containing untrusted users, as this is where the missing server-side authorization can be exploited

A user is affected if they are running any of the affected product versions AND the administrative interface is accessible to potential 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 6.4.15 / 7.0.13 / 7.2.6 or later
Fixed in 6.4.157.0.137.2.6
Interim mitigation

Apply the vendor-supplied patches from Fortinet for the affected versions. Until patches are applied, implement network segmentation and restrict administrative access to trusted IP addresses only.

Recommended fix High confidence

Upgrade to the latest version in your current branch: FortiAnalyzer/FortiManager 6.4.15+, 7.0.13+, 7.2.6+, or 7.4.3+; FortiAnalyzer Big Data 7.2.7+

  1. 1. Identify the currently installed Fortinet product (FortiAnalyzer, FortiAnalyzer Big Data, or FortiManager) and its exact version number using the CLI command: get system status
  2. 2. Based on the current version branch, plan the upgrade to the corresponding fixed release:
  3. - If on 6.4.x branch: upgrade to 6.4.15 or later
  4. - If on 7.0.x branch: upgrade to 7.0.13 or later
  5. - If on 7.2.x branch: upgrade to 7.2.6 or later
  6. - If on 7.4.x branch: upgrade to 7.4.3 or later
  7. 3. Download the firmware from the Fortinet Customer Support portal (https://support.fortinet.com)
  8. 4. Review the firmware upgrade release notes for any special migration or backup requirements
Caveat Standard Fortinet firmware upgrade considerations apply: review release notes for breaking changes, ensure backup, and plan maintenance window as upgrades may require reboot

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

Fix this in Fortianalyzer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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