CVE-2024-55590

8.8 HIGH

📋 TL;DR

This vulnerability allows authenticated attackers with read-only admin permissions and CLI access to execute arbitrary operating system commands on Fortinet FortiIsolator devices. Attackers can achieve remote code execution by crafting malicious CLI commands. Organizations running FortiIsolator versions 2.4.0 through 2.4.5 are affected.

💻 Affected Systems

Products:
  • Fortinet FortiIsolator
Versions: 2.4.0 through 2.4.5
Operating Systems: FortiOS-based appliance
Default Config Vulnerable: ⚠️ Yes
Notes: Requires authenticated user with at least read-only admin permissions and CLI access. All default configurations with these versions are vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full system compromise allowing attackers to install persistent backdoors, exfiltrate sensitive data, pivot to other network segments, and disrupt critical isolation functions.

🟠

Likely Case

Unauthorized access to isolated environments, data leakage from protected systems, and potential lateral movement within the network.

🟢

If Mitigated

Limited impact with proper network segmentation, minimal exposure, and strong authentication controls preventing unauthorized CLI access.

🌐 Internet-Facing: MEDIUM - While authentication is required, internet-facing FortiIsolator instances could be targeted if credentials are compromised or weak.
🏢 Internal Only: HIGH - Internal attackers or compromised accounts with CLI access can exploit this to bypass isolation controls and access protected systems.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Exploitation requires authenticated CLI access and knowledge of command injection techniques. No public exploit code is currently available.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: FortiIsolator version 2.4.6 or later

Vendor Advisory: https://fortiguard.fortinet.com/psirt/FG-IR-24-178

Restart Required: No

Instructions:

1. Download FortiIsolator version 2.4.6 or later from Fortinet support portal. 2. Backup current configuration. 3. Apply the firmware update through the web interface or CLI. 4. Verify the update completed successfully.

🔧 Temporary Workarounds

Restrict CLI Access

all

Limit CLI access to only essential administrative users and implement strong authentication controls.

Network Segmentation

all

Isolate FortiIsolator management interfaces from general network access and implement strict firewall rules.

🧯 If You Can't Patch

  • Implement strict access controls limiting CLI access to minimal required personnel
  • Monitor CLI command logs for suspicious patterns and implement alerting for command injection attempts

🔍 How to Verify

Check if Vulnerable:

Check FortiIsolator version via web interface (System > Dashboard) or CLI command 'get system status'

Check Version:

get system status | grep Version

Verify Fix Applied:

Verify version is 2.4.6 or later and test CLI command injection attempts that previously worked

📡 Detection & Monitoring

Log Indicators:

  • Unusual CLI command patterns
  • Multiple failed authentication attempts followed by CLI access
  • Commands containing shell metacharacters (;, |, &, $, etc.)

Network Indicators:

  • Unexpected outbound connections from FortiIsolator
  • Anomalous traffic patterns from management interfaces

SIEM Query:

source="fortiisolator" AND (command="*;*" OR command="*|*" OR command="*&*" OR command="*$*")

🔗 References

📤 Share & Export