CVE-2024-54026

4.3 MEDIUM

📋 TL;DR

This SQL injection vulnerability in Fortinet FortiSandbox allows attackers to execute unauthorized SQL commands via crafted HTTP requests. It affects multiple FortiSandbox versions including 4.4.0-4.4.6, 4.2, 4.0, 3.2, 3.1, 3.0, and FortiSandbox Cloud 24.1. Attackers could potentially execute arbitrary code or commands on vulnerable systems.

💻 Affected Systems

Products:
  • Fortinet FortiSandbox
  • Fortinet FortiSandbox Cloud
Versions: FortiSandbox 4.4.0 through 4.4.6, 4.2 all versions, 4.0 all versions, 3.2 all versions, 3.1 all versions, 3.0 all versions, FortiSandbox Cloud 24.1
Operating Systems: FortiOS-based appliances
Default Config Vulnerable: ⚠️ Yes
Notes: All default configurations of affected versions are vulnerable. The vulnerability requires HTTP access to the FortiSandbox management interface.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote code execution leading to complete system compromise, data exfiltration, and lateral movement within the network.

🟠

Likely Case

Database information disclosure, potential privilege escalation, and limited command execution depending on database permissions.

🟢

If Mitigated

Limited impact with proper network segmentation, database user restrictions, and input validation controls.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires crafting specific HTTP requests. The advisory suggests authentication may be required, but this isn't explicitly confirmed.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: FortiSandbox 4.4.7 or later, FortiSandbox Cloud 24.2 or later

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

Restart Required: Yes

Instructions:

1. Download the latest firmware from Fortinet support portal. 2. Backup current configuration. 3. Upload and install the firmware update via FortiSandbox web interface or CLI. 4. Reboot the system after installation completes.

🔧 Temporary Workarounds

Network Access Restriction

all

Restrict HTTP/HTTPS access to FortiSandbox management interface to trusted IP addresses only.

Configure firewall rules to allow only specific source IPs to access FortiSandbox management ports (typically 443/HTTPS)

Web Application Firewall

all

Deploy a WAF in front of FortiSandbox to filter SQL injection attempts.

Configure WAF rules to block SQL injection patterns targeting FortiSandbox endpoints

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate FortiSandbox from untrusted networks
  • Enable detailed logging and monitoring for SQL injection attempts on FortiSandbox interfaces

🔍 How to Verify

Check if Vulnerable:

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

Check Version:

execute get system status | grep Version

Verify Fix Applied:

Verify version is 4.4.7 or later for FortiSandbox, or 24.2 or later for FortiSandbox Cloud

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • HTTP requests with SQL syntax in parameters
  • Failed authentication attempts followed by SQL-like payloads

Network Indicators:

  • HTTP requests containing SQL keywords (SELECT, UNION, INSERT, etc.) to FortiSandbox management interface

SIEM Query:

source="fortisandbox" AND (http_uri="*sql*" OR http_uri="*union*" OR http_uri="*select*" OR http_uri="*insert*")

🔗 References

📤 Share & Export