dbcve.org
FortianalyzerApplication · Fortinet

CVE-2024-35275

HIGH · 8.8 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 7.4.3 / 7.4.4 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 improper neutralization of special elements used in an sql command ('sql injection') in Fortinet FortiAnalyzer version 7.4.0 through 7.4.2, FortiManager version 7.4.0 through 7.4.2 allows attacker to escalation of privilege via specially crafted http 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

SQL injection vulnerability in FortiAnalyzer and FortiManager versions 7.4.0-7.4.2 allows attackers to escalate privileges through specially crafted HTTP requests due to improper neutralization of special elements in SQL commands.

MitigationUpgrade to Fortinet's patched version (contact Fortinet support for availability). If immediate patching is not possible, implement web application firewall rules to detect and block SQL injection attempts in HTTP requests.

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:>= 7.4.0, < 7.4.4
Fortianalyzer CloudApplication
Affected:>= 7.4.1, < 7.4.3
FortimanagerApplication
Affected:>= 7.4.0, < 7.4.3
Fortimanager CloudApplication
Affected:>= 7.4.1, < 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 product and version
    Run 'get system status' in FortiAnalyzer/FortiManager CLI or check the web UI dashboard for the firmware version displayed under System Information
    Affected if The product is FortiAnalyzer or FortiManager and the version falls within 7.4.0-7.4.3 for FMG/Faz or 7.4.0-7.4.3 for Faz Cloud or 7.4.1-7.4.2 for Faz Cloud (exact range depends on product)
  2. Verify web UI or REST API is enabled
    Run 'get system interface' in CLI to list enabled interfaces, then check 'get system web-ui' to see if the web UI service is enabled
    Affected if The HTTP/HTTPS service (web UI or REST API) is enabled on any management interface accessible to attackers
  3. Confirm network exposure
    Review interface bindings with 'config system interface' then 'show' to identify which interfaces have https or http service enabled, then determine if those interfaces are reachable from untrusted networks
    Affected if The management interface with web UI enabled is bound to a physical interface or VLAN accessible from external or untrusted networks
  4. Check for exploitation indicators
    Review logs for SQL injection patterns: search in 'log viewer' or run 'execute log filter' looking for SQL keywords (SELECT, UNION, INSERT) in URL parameters, or check 'fdslog' for anomaly indicators
    Affected if HTTP request logs contain suspicious SQL syntax in URI parameters or body that suggest exploitation attempts

You are affected if you are running FortiAnalyzer or FortiManager version 7.4.0 through 7.4.3 (or the specific cloud version range) with the web UI or REST API enabled and accessible, especially if 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.4.3 / 7.4.4 or later
Fixed in 7.4.37.4.4
Interim mitigation

Upgrade to Fortinet's patched version (contact Fortinet support for availability). If immediate patching is not possible, implement web application firewall rules to detect and block SQL injection attempts in HTTP requests.

Recommended fix High confidence

FortiAnalyzer: upgrade to 7.4.4 or later | FortiAnalyzer Cloud: upgrade to 7.4.3 or later | FortiManager: upgrade to 7.4.3 or later | FortiManager Cloud: upgrade to 7.4.3 or later

  1. 1. Backup FortiAnalyzer/FortiManager configuration before upgrading
  2. 2. Download the appropriate firmware version from Fortinet support portal: FortiAnalyzer 7.4.4 or later, FortiManager 7.4.3 or later
  3. 3. Access FortiAnalyzer/FortiManager via CLI or web interface
  4. 4. Upload and install the firmware upgrade following Fortinet's standard upgrade procedure
  5. 5. Verify the upgrade was successful and the SQL injection vulnerability is resolved
  6. 6. Confirm normal operation and all services are functioning after upgrade
Caveat Review Fortinet release notes for 7.4.3/7.4.4 for any configuration or feature changes before upgrading

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

Fix this in Fortianalyzer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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