dbcve.org
FortianalyzerApplication · Fortinet

CVE-2024-32118

MEDIUM · 6.7 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 →
69/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 improper neutralization of special elements used in an OS command ('OS Command Injection') vulnerabilities [CWE-78] in Fortinet FortiManager version 7.4.0 through 7.4.2 and before 7.2.5, Fortinet FortiAnalyzer version 7.4.0 through 7.4.2 and before 7.2.5 and Fortinet FortiAnalyzer-BigData before 7.4.0 allows an authenticated privileged attacker to execute unauthorized code or commands 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

OS Command Injection vulnerability in FortiManager and FortiAnalyzer allows authenticated privileged attackers to execute unauthorized commands via crafted CLI requests. The flaw exists in multiple locations where special elements are not properly neutralized before being passed to OS command execution.

MitigationUpgrade FortiManager to version 7.4.3 or 7.2.5 and above, and FortiAnalyzer to version 7.4.3 or 7.2.5 and above. Apply Fortinet's published patches and verify no unauthorized commands can be executed through the CLI interface.

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
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? 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 type and version
    Run the command 'get system status' in the CLI or check the web UI dashboard for the FortiManager or FortiAnalyzer model and firmware version
    Affected if The device is FortiManager or FortiAnalyzer (including Big Data) and the version falls within 6.2.0 to 7.2.5, 7.4.0 to 7.4.2, or 7.2.6 to 7.2.7 (for Big Data)
  2. Verify CLI access is enabled
    Check in web UI under System > Admin > Administrators or run 'get system admin user' in CLI to list admin accounts and their access methods
    Affected if CLI access (via SSH, console, or web-based CLI) is permitted for privileged users
  3. Confirm privileged user presence
    Review the administrator accounts list and their profiles using 'get system admin user' in CLI, noting which accounts have privileged profiles such as 'super_admin' or 'admin'
    Affected if There are authenticated privileged administrator accounts configured on the device
  4. Review CLI command audit logs
    Run 'execute log filter category 1' then 'execute log display' or check the Log Analysis pane in web UI for CLI command execution entries from the Event Management module
    Affected if There are unauthorized or suspicious CLI commands executed that were not initiated by legitimate administrators

You are affected if the device is FortiManager or FortiAnalyzer running a version within the affected ranges AND CLI interface is accessible to authenticated privileged users.

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

Upgrade FortiManager to version 7.4.3 or 7.2.5 and above, and FortiAnalyzer to version 7.4.3 or 7.2.5 and above. Apply Fortinet's published patches and verify no unauthorized commands can be executed through the CLI interface.

Recommended fix High confidence

FortiManager: upgrade to 7.2.6+ or 7.4.3+ | FortiAnalyzer: upgrade to 7.2.6+ or 7.4.3+ | FortiAnalyzer-Big Data: upgrade to 7.4.0+

  1. 1. Identify the currently installed FortiManager/FortiAnalyzer/FortiAnalyzer-Big Data version using the CLI command: get system status
  2. 2. For FortiManager or FortiAnalyzer: If running 7.4.x branch, upgrade to version 7.4.3 or later
  3. 3. For FortiManager or FortiAnalyzer: If running 7.2.x branch, upgrade to version 7.2.6 or later
  4. 4. For FortiAnalyzer-Big Data: If running any version before 7.4.0, upgrade to version 7.4.0 or later
  5. 5. After upgrade, verify the fix by checking the version: get system status
  6. 6. Confirm the vulnerability is resolved by reviewing FortiGuard release notes for CVE-2024-32118
Caveat Review FortiManager/FortiAnalyzer release notes for compatibility notes and any configuration changes required between versions

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

Fix this in Fortianalyzer Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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