dbcve.org
FortianalyzerApplication · Fortinet

CVE-2024-32116

MEDIUM · 6.0 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 7.2.6 / 7.2.8 or later.
See remediation →
62/100
Remediation priority · Elevated
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
Multiple relative path traversal vulnerabilities [CWE-23] in Fortinet FortiManager version 7.4.0 through 7.4.2 and before 7.2.5, FortiAnalyzer 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 delete files from the underlying filesystem via crafted CLI 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 · high confidence

This CVE addresses multiple relative path traversal vulnerabilities (CWE-23) in FortiManager, FortiAnalyzer, and FortiAnalyzer-BigData. A privileged attacker can exploit crafted CLI requests to traverse directories and delete arbitrary files on the underlying filesystem, bypassing intended access restrictions.

MitigationApply the vendor-supplied patches: upgrade FortiManager and FortiAnalyzer to version 7.2.5 or later (7.4.x to 7.4.3+), and FortiAnalyzer-BigData to 7.2.7 or later. Review privileged CLI access controls as a defense-in-depth measure.

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.2.0, < 7.2.6>= 7.4.0, < 7.4.3
Fortianalyzer Big DataApplication
Affected:>= 6.2.1, < 7.2.8= 7.4.0
FortimanagerApplication
Affected:>= 6.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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/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 product and version
    Run the CLI command: `get system status` or `diagnose system version`. This displays the installed FortiManager or FortiAnalyzer version, model, and build number.
    Affected if The version falls within FortiAnalyzer >= 6.2.0 and < 7.2.6, or >= 7.4.0 and < 7.4.3; FortiAnalyzer Big Data >= 6.2.1 and < 7.2.8, or = 7.4.0; or FortiManager >= 6.2.0 and < 7.2.6, or >= 7.4.0 and < 7.4.3.
  2. Confirm the exact product variant
    The `get system status` output includes the product name. Verify whether the device is FortiManager, FortiAnalyzer, or FortiAnalyzer-BigData because version ranges differ slightly between these products.
    Affected if The product is FortiAnalyzer-BigData and the version is 7.4.0 (specific to Big Data only), or any other version matching the affected ranges for that product.
  3. Check for privileged CLI access
    Review the admin user configuration by running: `get system admin user` and examine which users have privileged access. Also check `show system accprofile` for profiles with CLI execute permissions.
    Affected if Privileged CLI accounts exist (users with super_admin or custom profiles allowing CLI file operations), as the vulnerability is exploited through crafted CLI requests.
  4. Review CLI command logging
    Check logs for suspicious file operations via CLI: `execute log filter category event` followed by `execute log display` or review logs under Log & Report > Event Log > CLI. Look for file deletion or traversal-related commands.
    Affected if Unusual or unauthorized CLI commands performing file operations (delete, remove, or path traversal patterns like ../) appear in the logs.

Your environment is affected if the installed FortiManager, FortiAnalyzer, or FortiAnalyzer-BigData version falls within the affected ranges AND privileged CLI access is available to any user.

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.6 / 7.2.8 / 7.4.3 or later
Fixed in 7.2.67.2.87.4.3
Interim mitigation

Apply the vendor-supplied patches: upgrade FortiManager and FortiAnalyzer to version 7.2.5 or later (7.4.x to 7.4.3+), and FortiAnalyzer-BigData to 7.2.7 or later. Review privileged CLI access controls as a defense-in-depth measure.

Recommended fix High confidence

FortiManager/FortiAnalyzer: upgrade to 7.2.6 or 7.4.3 (or later); FortiAnalyzer Big Data: upgrade to 7.2.8 or 7.4.1 (or later)

  1. 1. Identify the currently installed FortiManager/FortiAnalyzer version using the CLI command 'get system status' or through the web UI dashboard
  2. 2. Determine which firmware branch (7.2.x or 7.4.x) is appropriate for your environment based on your migration/upgrade plan
  3. 3. For FortiManager: upgrade to version 7.2.6 or 7.4.3 or later
  4. 4. For FortiAnalyzer: upgrade to version 7.2.6 or 7.4.3 or later
  5. 5. For FortiAnalyzer Big Data: upgrade to version 7.2.8 or 7.4.1 or later
  6. 6. Download the firmware from Fortinet Customer Support portal (https://support.fortinet.com)
  7. 7. Upload the firmware via the FortiAnalyzer/FortiManager web UI under System > Firmware or via CLI using 'execute firmware upload'
  8. 8. After upgrade, verify the new version is installed using 'get system status'
Caveat Standard firmware upgrade risks apply - review release notes for migration considerations and test in non-production environment before deploying

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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