dbcve.org
FortiisolatorWeb server / proxy · Fortinet

CVE-2024-54024

HIGH · 7.2 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 2.4.7 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 FortiIsolator before version 2.4.6 allows a privileged attacker with super-admin profile and CLI access to execute unauthorized code via specifically 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 · high confidence

OS command injection vulnerability in FortiIsolator allows authenticated super-admin users to execute arbitrary OS commands via specifically crafted HTTP requests due to improper neutralization of special elements in user input.

MitigationUpgrade FortiIsolator to version 2.4.6 or later to patch the command injection vulnerability.

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
FortiisolatorWeb server / proxy
Affected:>= 2.4.3, < 2.4.7

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 FortiIsolator installation
    Locate the FortiIsolator appliance or software installation in your environment. Check system documentation or asset inventory for FortiIsolator entries.
    Affected if FortiIsolator is present in the environment
  2. Determine installed FortiIsolator version
    Access the FortiIsolator web interface or CLI and retrieve the firmware/software version. In the web GUI, navigate to Dashboard > System Information > Firmware Version. Via CLI, use the command 'get system status' or 'diagnose system version'.
    Affected if Installed version is 2.4.3, 2.4.4, 2.4.5, or any 2.4.x version below 2.4.7
  3. Verify super-admin user accounts exist
    In the FortiIsolator web interface, go to System > Administrators > Admin Users. Check if any accounts with 'Super Admin' profile exist. Via CLI, use 'get system admin user' to list administrator accounts.
    Affected if Super-admin accounts are configured and enabled
  4. Confirm web management interface is exposed
    Verify that the FortiIsolator HTTP/HTTPS management interface is accessible from network locations where potential attackers could send crafted requests. Check firewall rules and interface bindings.
    Affected if Web interface is accessible on network segments accessible to untrusted users, even if authenticated

Environment is affected if FortiIsolator version is 2.4.3 through 2.4.6 (any version >= 2.4.3 but < 2.4.7), the HTTP management interface is network-accessible, and super-admin user accounts exist.

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 2.4.7 or later
Fixed in 2.4.7
Interim mitigation

Upgrade FortiIsolator to version 2.4.6 or later to patch the command injection vulnerability.

Recommended fix High confidence

FortiIsolator version 2.4.7 (or latest stable version >= 2.4.6)

  1. 1. Identify the current FortiIsolator version by accessing the CLI or web interface.
  2. 2. Confirm the installed version is >= 2.4.3 and < 2.4.6 (or < 2.4.7 if 2.4.6 is also affected).
  3. 3. Download FortiIsolator version 2.4.7 (or the latest stable version >= 2.4.6) from the Fortinet Customer Support Portal: https://support.fortinet.com/.
  4. 4. Review the upgrade release notes for any special instructions or prerequisites.
  5. 5. Back up the current FortiIsolator configuration before proceeding with the upgrade.
  6. 6. Schedule a maintenance window as the upgrade may require a system restart.
  7. 7. Apply the firmware upgrade through the FortiIsolator web interface or CLI using the firmware upload functionality.
  8. 8. After upgrade completion, verify the new version is running and confirm the system is operational.
Caveat Review release notes for any breaking changes between current and new version; some configurations may need adjustment after upgrade.

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

Fix this in Fortiisolator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
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,488.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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