dbcve.org
FortiisolatorWeb server / proxy · Fortinet

CVE-2024-54025

MEDIUM · 6.7 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 2.4.7 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
An improper neutralization of special elements used in an OS command ('OS Command Injection') vulnerability [CWE-78] in Fortinet FortiIsolator CLI before version 2.4.6 allows a 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

FortiIsolator CLI before version 2.4.6 contains an OS command injection vulnerability (CWE-78) where improper neutralization of special elements allows a privileged attacker to execute unauthorized operating system commands through crafted CLI requests. The attacker requires authenticated privileged access to the FortiIsolator device.

MitigationUpgrade FortiIsolator to version 2.4.6 or later. Until patched, restrict CLI access to only trusted, privileged users and monitor for suspicious command patterns.

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
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 FortiIsolator installation
    Locate FortiIsolator on the system by checking for its CLI executable, service, or management interface. Common methods include searching for 'fortiisolator' in installed packages, running processes, or checking /opt/ for Fortinet installations.
    Affected if FortiIsolator software is found running or installed on the system
  2. Determine installed version
    Run the FortiIsolator CLI command to retrieve the system version. Typically this involves executing 'get system status' or 'diagnose system version' within the FortiIsolator CLI console, or checking the firmware file if upgrading from ISO.
    Affected if The reported version falls within >= 2.4.3 and < 2.4.7
  3. Confirm CLI access is enabled
    Verify that the FortiIsolator CLI service is accessible. Check the administrative interface configuration via 'show system interface' or similar CLI commands to confirm CLI ports (typically SSH on port 22 or HTTP/HTTPS) are listening and enabled.
    Affected if CLI access is enabled and reachable on the network
  4. Audit privileged CLI user access
    Review the list of configured privileged users with CLI access using 'get system admin' or similar administrative commands. Identify all accounts with privilege level sufficient to execute CLI commands.
    Affected if Multiple privileged users exist or unauthorized privileged accounts are present
  5. Check for suspicious command patterns
    Review CLI command logs, audit logs, or system logs for unusual or unexpected commands executed through the CLI interface. Look for indicators such as commands containing shell metacharacters (;, |, &, $) or unexpected program execution calls.
    Affected if Log analysis reveals CLI commands that are unusual, unauthorized, or contain suspicious patterns consistent with injection attempts

A user is affected if FortiIsolator version 2.4.3 through 2.4.6 is installed and the 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 2.4.7 or later
Fixed in 2.4.7
Interim mitigation

Upgrade FortiIsolator to version 2.4.6 or later. Until patched, restrict CLI access to only trusted, privileged users and monitor for suspicious command patterns.

Recommended fix High confidence

FortiIsolator 2.4.6 or later

  1. 1. Identify the current FortiIsolator version by accessing the CLI or web interface
  2. 2. Confirm the current version is >= 2.4.3 and < 2.4.6
  3. 3. Download FortiIsolator version 2.4.6 or later from the Fortinet support portal (support.fortinet.com)
  4. 4. Review the upgrade procedure in the FortiIsolator administration guide
  5. 5. Execute the upgrade following the documented procedure, preferably during a maintenance window
  6. 6. After upgrade, verify the new version is 2.4.6 or higher
  7. 7. Confirm the vulnerability is resolved by checking the FortiGuard advisory for CVE-2024-54025

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

Fix this in Fortiisolator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,600
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,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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