dbcve.org
Fortimanager CloudApplication · Fortinet

CVE-2024-40584

HIGH · 7.2 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 7.2.6 / 7.2.8 or later.
See remediation →
78/100
Remediation priority · High
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
An improper neutralization of special elements used in an OS command ('OS Command Injection') vulnerability [CWE-78] in Fortinet FortiAnalyzer version 7.4.0 through 7.4.3, 7.2.0 through 7.2.5, 7.0.0 through 7.0.13, 6.4.0 through 6.4.15 and 6.2.2 through 6.2.13, Fortinet FortiManager version 7.4.0 through 7.4.3, 7.2.0 through 7.2.5, 7.0.0 through 7.0.13, 6.4.0 through 6.4.15 and 6.2.2 through 6.2.13, Fortinet FortiAnalyzer BigData version 7.4.0, 7.2.0 through 7.2.7, 7.0.1 through 7.0.6, 6.4.5 through 6.4.7 and 6.2.5, Fortinet FortiAnalyzer Cloud version 7.4.1 through 7.4.3, 7.2.1 through 7.2.5, 7.0.1 through 7.0.13 and 6.4.1 through 6.4.7 and Fortinet FortiManager Cloud version 7.4.1 through 7.4.3, 7.2.1 through 7.2.5, 7.0.1 through 7.0.13 and 6.4.1 through 6.4.7 GUI allows an authenticated privileged attacker to execute unauthorized code or commands via crafted HTTPS or 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 · high confidence

OS command injection vulnerability in FortiAnalyzer and FortiManager GUI allows authenticated privileged attackers to execute arbitrary OS commands via crafted HTTPS/HTTP requests. The flaw stems from improper neutralization of special elements in user-supplied input being passed to system shell commands.

MitigationApply Fortinet patches/updates to the latest supported versions for all affected products. Limit GUI administrative access to trusted networks and privileged users only.

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
Fortimanager CloudApplication
Affected:>= 6.4.1, <= 7.0.14>= 7.2.1, < 7.2.6>= 7.4.1, < 7.4.4
FortimanagerApplication
Affected:>= 6.2.2, <= 6.2.13>= 6.4.0, < 7.2.6>= 7.4.0, < 7.4.4
Fortianalyzer Big DataApplication
Affected:>= 6.2.1, < 7.2.8= 7.4.0
Fortianalyzer CloudApplication
Affected:>= 6.4.1, < 7.2.6>= 7.4.1, < 7.4.4
FortianalyzerApplication
Affected:>= 6.2.2, < 7.2.6>= 7.4.0, < 7.4.4

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 the installed Fortinet product and version
    Run the following CLI command on the device: 'get system status' or 'fnsysctl get system status' to display the product name and firmware version.
    Affected if The product is FortiManager or FortiAnalyzer and the version falls within any of the affected ranges: FortiManager >= 6.2.2 <= 6.2.13, >= 6.4.0 < 7.2.6, >= 7.4.0 < 7.4.4; FortiManager Cloud >= 6.4.1 <= 7.0.14, >= 7.2.1 < 7.2.6, >= 7.4.1 < 7.4.4; FortiAnalyzer >= 6.2.2 < 7.2.6, >= 7.4.0 < 7.4.4; Fort
  2. Verify GUI administrative access is enabled
    Run the CLI command: 'get system interface' or check via 'show system interface' to see if the management interface has HTTP/HTTPS services enabled.
    Affected if The GUI service (HTTP or HTTPS) is enabled on any accessible interface, as this vulnerability is exploitable through crafted HTTPS/HTTP requests to the GUI.
  3. Check GUI access policy and network exposure
    Run: 'get firewall policy' or 'show firewall policy' to review policies controlling GUI access, and verify the source addresses permitted to reach the GUI interface.
    Affected if The GUI is reachable from untrusted networks or there are no strict source IP restrictions on administrative access to the GUI interface.
  4. Confirm presence of privileged administrative accounts
    Run: 'get admin user' or 'show system admin' to list administrative users and their privilege levels.
    Affected if There are privileged administrative accounts configured, as the CVE requires authenticated privileged attackers to exploit the command injection.

You are affected if you are running FortiAnalyzer or FortiManager with GUI enabled and your firmware version falls within the affected ranges listed, regardless of GUI network exposure since the vulnerability is present in the code.

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.4 or later
Fixed in 7.2.67.2.87.4.4
Interim mitigation

Apply Fortinet patches/updates to the latest supported versions for all affected products. Limit GUI administrative access to trusted networks and privileged users only.

Recommended fix High confidence

FortiManager/FortiAnalyzer: 7.4.4 (or 7.2.6, 7.0.14, 6.4.16, or 6.2.14 depending on your current branch) | FortiManager Cloud/FortiAnalyzer Cloud: 7.4.4, 7.2.6, 7.0.14, 6.4.16, or 6.2.14 | FortiAnalyzer Big Data: 7.4.4, 7.2.8, 7.0.7, 6.4.8, or 6.2.6

  1. 1. Identify the currently installed FortiAnalyzer, FortiManager, or FortiAnalyzer/Manager Cloud version using the web GUI (System Settings > Dashboard > System Information) or CLI: get system status
  2. 2. Based on your current major version branch, plan the upgrade to the first fixed version in that branch: For 7.4.x branch, upgrade to 7.4.4; For 7.2.x branch, upgrade to 7.2.6; For 7.0.x branch, upgrade to 7.0.14; For 6.4.x branch, upgrade to 6.4.16; For 6.2.x branch, upgrade to 6.2.14
  3. 3. Before upgrading, backup the current configuration via GUI (System Settings > Maintenance > Backup) or CLI: execute backup config
  4. 4. Download the appropriate firmware image from Fortinet Customer Support portal for your specific product model
  5. 5. Upload and install the firmware via GUI (System Settings > Firmware > Upload) or CLI: execute system firmware-upgrade
  6. 6. After reboot, verify the upgrade was successful and the new version matches the expected fixed version: get system status
  7. 7. Validate that the GUI functionality and core features are working as expected
Caveat Review Fortinet release notes for your target version to check for configuration changes, feature modifications, or known upgrade issues before proceeding

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

Fix this in Fortimanager Cloud Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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