FortianalyzerApplication · Fortinet

CVE-2024-33501

MEDIUM · 6.7 CVSS v3.1 Published 2025-03-11

Fix available

A fix is available. Upgrade to 7.2.6 / 7.2.8 or later.

See remediation →

69/100

Remediation priority · Elevated

Zero-click

Official description

NVD · unedited

Two improper neutralization of special elements used in an SQL Command ('SQL Injection') vulnerability [CWE-89] in Fortinet FortiAnalyzer version 7.4.0 through 7.4.2 and before 7.2.5, FortiManager version 7.4.0 through 7.4.2 and before 7.2.5 and FortiAnalyzer-BigData version 7.4.0 and before 7.2.7 allows a privileged attacker to execute unauthorized code or commands via specifically crafted CLI requests.

Technical summary

dbcve analysis · high confidence

SQL injection vulnerability in Fortinet FortiAnalyzer, FortiManager, and FortiAnalyzer-BigData allows a privileged attacker to execute unauthorized code or commands via specially crafted CLI requests. The flaw exists in the CLI interface where user input is improperly neutralized before being used in SQL queries.

MitigationApply Fortinet security patches: upgrade to FortiAnalyzer/FortiManager 7.4.3 or later (or 7.2.5+), and FortiAnalyzer-BigData 7.2.7 or later. Until patched, strictly limit CLI access to trusted privileged users only and monitor for suspicious CLI activity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

FortianalyzerApplication

Affected:>= 6.4.0, < 7.2.6>= 7.4.0, < 7.4.3

Fortianalyzer Big DataApplication

Affected:>= 6.4.5, < 7.2.8= 7.4.0

FortimanagerApplication

Affected:>= 6.0.10, <= 6.0.12>= 6.2.8, < 7.2.6>= 7.4.0, < 7.4.3

CVSS breakdown

From the vector

Attack vector: Local
Complexity: Low
Privileges: High
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify the installed Fortinet product

Run 'get system status' or 'fnsysctl get system status' via CLI, or check the web UI dashboard for the product name

Affected if The product is FortiAnalyzer, FortiAnalyzer-BigData, or FortiManager
Determine the installed version

Run 'get system status' or 'fnsysctl get system status' via CLI to display the firmware version number

Affected if The version falls within: FortiAnalyzer >= 6.4.0 and < 7.2.6, or >= 7.4.0 and < 7.4.3; FortiAnalyzer-BigData >= 6.4.5 and < 7.2.8, or = 7.4.0; FortiManager >= 6.0.10 through 6.0.12, >= 6.2.8 and < 7.2.6, or >= 7.4.0 and < 7.4.3
Verify CLI interface accessibility

Confirm that CLI access is enabled via 'show system interface' and check that admin accounts have CLI privileges in 'show system admin'

Affected if CLI access is permitted to any admin or privileged user account
Review admin user privileges

Execute 'show system admin' to list admin accounts and their privilege levels

Affected if Multiple admin accounts or service accounts with privileged access exist
Inspect CLI command logs for suspicious activity

Check log outputs for unusual SQL-like commands or abnormal CLI query patterns in the event log orfortiAnalyzer/FortiManager logs

Affected if Logs contain unexpected or malformed SQL commands issued via CLI interface

Your environment is affected if you are running FortiAnalyzer, FortiAnalyzer-BigData, or FortiManager with a version matching the affected ranges and the CLI interface is accessible to privileged users.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 7.2.6 / 7.2.8 / 7.4.3 or later

Fixed in 7.2.67.2.87.4.3

Interim mitigation

Apply Fortinet security patches: upgrade to FortiAnalyzer/FortiManager 7.4.3 or later (or 7.2.5+), and FortiAnalyzer-BigData 7.2.7 or later. Until patched, strictly limit CLI access to trusted privileged users only and monitor for suspicious CLI activity.

Recommended fix High confidence

FortiAnalyzer: upgrade to 7.2.6 or 7.4.3; FortiAnalyzer Big Data: upgrade to 7.2.8 or 7.4.1; FortiManager: upgrade to 7.2.6 or 7.4.3

1. Identify the exact FortiAnalyzer/FortiManager version currently installed using: `get system status` or `fnmsys` command
2. For FortiAnalyzer: upgrade to version 7.2.6 or later (if on 7.2.x branch), or 7.4.3 or later (if on 7.4.x branch)
3. For FortiAnalyzer Big Data: upgrade to version 7.2.8 or later (if on 7.2.x branch), or 7.4.1 or later (if on 7.4.x branch)
4. For FortiManager: upgrade to version 7.2.6 or later (if on 7.2.x branch), or 7.4.3 or later (if on 7.4.x branch)
5. Download the appropriate firmware from Fortinet Customer Support portal (https://support.fortinet.com)
6. Upload the firmware to the device via Web UI (System > Firmware) or CLI: `execute restore config` or `execute upgrade`
7. Reboot the device after upgrade completes
8. Verify the new version is installed: `get system status`

Caveat Review Fortinet release notes for 7.2.6/7.4.3 for any configuration or feature changes before upgrading; ensure backup of current configuration is available

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

Fix this in Fortianalyzer Scoped from the published advisory

Consultation4.0 h
Implementation6.0 h
Testing4.0 h
Review / QA2.0 h

16.0 hours of engineering $2,840

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,544.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

fortiguard.fortinet.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-33501 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-33501?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 7.2.6 / 7.2.8 or later

Severity 6.7 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Affects: Fortianalyzer

Remediation

Need this fixed?

Fix this in Fortianalyzer 16 hrs · Moderate

Typical engagement from $2,840

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2024-33501 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References