CVE-2024-23666
Fortinet Fortianalyzer 6.4.0 – 6.4.15
Raw vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-23666 is a high-severity Client-Side Enforcement of Server-Side Security (CWE-602) vulnerability in Fortinet Fortianalyzer. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 15% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-25 (Reference Monitor) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-23666 is a client-side enforcement of server-side security flaw, tracked under CWE-602, that permits improper access control in multiple Fortinet products. Affected components include FortiAnalyzer-BigData versions 7.4.0 and 7.2.0 through 7.2.6, 7.0.1 through 7.0.6, 6.4.5 through 6.4.7, and 6.2.5; FortiManager versions 7.4.0 through 7.4.1, 7.2.0 through 7.2.4, 7.0.0 through 7.0.11, and 6.4.0 through 6.4.14; and FortiAnalyzer versions 7.4.0 through 7.4.1, 7.2.0 through 7.2.4, 7.0.0 through 7.0.11, and 6.4.0 through 6.4.14. The issue carries a CVSS 3.1 score of 7.5.
An authenticated attacker with network access can submit crafted requests to bypass intended server-side controls and obtain high-impact access to confidentiality, integrity, and availability. Exploitation requires low attack complexity once low-privileged credentials are obtained and does not depend on user interaction.
The Fortinet advisory FG-IR-23-396 addresses the vulnerability. Current EPSS stands at 0.0813 after reaching a peak of 0.1029.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-21139
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V10.7.1V2.2.2V8.3.1V10.4.1
Mitigating Controls (NIST 800-53 r5) AI
Requires a tamper-proof, always-invoked reference monitor that cannot be bypassed by client-side logic.
Enforces all access decisions on the server according to policy rather than trusting client-supplied enforcement.
Enforces information-flow rules at the server boundary instead of delegating them to the client.
Monitors and controls all external and key internal interfaces so that server-side policy cannot be off-loaded to clients.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure architecture principles discourage client-side trust but do not directly address this weakness.
Security testing can detect client-side enforcement but is not the primary mitigation.
Information access restriction is undermined when the client is trusted to enforce it.
Secure development lifecycle mandates server-side validation and prevents reliance on client enforcement.
Application security requirements explicitly call for server-side enforcement of security mechanisms.
Secure coding standards require server-side checks and reject client-only enforcement.