dbcve.org
FortiisolatorWeb server / proxy · Fortinet

CVE-2024-55590

HIGH · 8.8 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to 2.4.6 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Multiple improper neutralization of special elements used in an OS command ('OS Command Injection') vulnerabilities [CWE-78] in Fortinet FortiIsolator version 2.4.0 through 2.4.5 allows an authenticated attacker with at least read-only admin permission and CLI access to execute unauthorized code via specifically crafted CLI commands.

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 Fortinet FortiIsolator versions 2.4.0-2.4.5 allows authenticated attackers with read-only admin privileges and CLI access to execute unauthorized OS commands through specially crafted CLI commands, achieving arbitrary code execution on the appliance.

MitigationUpgrade FortiIsolator to version 2.4.6 or later to remediate the OS command injection vulnerabilities. Restrict CLI access to only necessary personnel and follow least-privilege principles for admin accounts.

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.0, < 2.4.6

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

CVSS:3.1/AV:N/AC:L/PR:L/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
    Check for FortiIsolator appliance in your environment inventory or network documentation. Look for devices running FortiIsolator software.
    Affected if FortiIsolator is not present in your environment, you are not affected.
  2. Determine installed FortiIsolator version
    Access the FortiIsolator CLI or web interface and run the command: get system status. Alternatively, check the firmware file name or use FortiIsolator's built-in version check feature.
    Affected if Version is 2.4.0 through 2.4.5 inclusive, indicating vulnerability to CVE-2024-55590.
  3. Verify CLI access is enabled
    From the FortiIsolator web interface, go to System > Admin > Administrators to check if CLI access is granted to any admin accounts. In the CLI, run: get system admin list to see admin accounts with CLI privileges.
    Affected if CLI access is enabled for any admin account (including read-only accounts), creating the attack surface for this vulnerability.
  4. Confirm admin account privileges
    Review all admin accounts in FortiIsolator: in web UI navigate to System > Admin > Administrators, or run: get system admin in CLI. Note which accounts have 'Read-Write' or 'Read-Only' access levels.
    Affected if Any authenticated admin account (read-only or higher) exists with CLI access, satisfying the authentication requirement for exploitation.
  5. Check for unauthorized CLI command execution evidence
    Review FortiIsolator system logs and audit logs for unusual CLI commands. Use: execute log filter category event, then execute log view to look for unexpected execute commands or shell invocations.
    Affected if Unusual or unauthorized CLI commands appear in logs, potentially indicating exploitation attempts.

You are affected if FortiIsolator version 2.4.0-2.4.5 is installed and CLI access is enabled for any authenticated admin account, allowing command injection via specially crafted CLI commands.

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.6 or later
Fixed in 2.4.6
Interim mitigation

Upgrade FortiIsolator to version 2.4.6 or later to remediate the OS command injection vulnerabilities. Restrict CLI access to only necessary personnel and follow least-privilege principles for admin accounts.

Recommended fix High confidence

FortiIsolator 2.4.6

  1. 1. Log in to the FortiIsolator admin interface or access via console/SSH with administrator credentials.
  2. 2. Navigate to System > Firmware or use the 'execute upgrade' CLI command to initiate the firmware upgrade.
  3. 3. Download the firmware image for FortiIsolator version 2.4.6 from the Fortinet Customer Service & Support portal (https://support.fortinet.com).
  4. 4. Upload the firmware version 2.4.6 to the FortiIsolator device.
  5. 5. Confirm the upgrade and allow the device to reboot. Verify the new version is 2.4.6 after the reboot.
  6. 6. Verify that the OS command injection vulnerability is remediated by confirming the version and testing that CLI commands with special characters are properly sanitized.

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

Fix this in Fortiisolator Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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