FortisandboxApplication · Fortinet
CVE-2024-21755
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 · uneditedA improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet FortiSandbox 4.4.0 through 4.4.3, FortiSandbox 4.2.1 through 4.2.6, FortiSandbox 4.0.0 through 4.0.4 allows attacker to execute unauthorized code or commands via crafted 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 · moderate confidenceOS command injection vulnerability in Fortinet FortiSandbox allows remote attackers to execute unauthorized OS commands via crafted HTTP requests. Affected versions include 4.0.0 through 4.0.4, 4.2.1 through 4.2.6, and 4.4.0 through 4.4.3. The vulnerability stems from improper neutralization of special elements in OS command execution.
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
FortisandboxApplication
>= 4.0.0, < 4.0.5>= 4.2.0, < 4.2.7>= 4.4.0, < 4.4.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify FortiSandbox installation and versionAccess the FortiSandbox CLI or web interface and retrieve the system version information. In CLI, this is typically done using 'get system status' or 'diagnose system version' commands. In the web interface, check the Dashboard or System > Settings page for the firmware version.Affected if The installed version falls within 4.0.0-4.0.4, 4.2.0-4.2.6, or 4.4.0-4.4.3 (or starts with 4.2.1-4.2.6 or 4.4.1-4.4.3 based on the specific vulnerable ranges)
-
Verify HTTP management interface accessibilityDetermine if the FortiSandbox HTTP/HTTPS management interface is exposed to untrusted networks. Check network configuration to see if port 80 or 443 (or custom HTTP service ports) are accessible from external or untrusted IP addresses.Affected if The HTTP management interface is exposed to untrusted networks, as the vulnerability is exploited via crafted HTTP requests
-
Review system logs for suspicious HTTP activityExamine FortiSandbox log files for unusual or unexpected HTTP requests that may indicate command injection attempts. Use 'execute log traffic' or check System > Log > Traffic logs for anomalies in HTTP parameter values.Affected if Logs show unexpected or malformed HTTP requests containing shell metacharacters or suspicious parameter patterns
-
Check for unexpected system processes or artifactsMonitor for new or unexpected processes running on the FortiSandbox system that were not initiated by known legitimate activities. Look for suspicious files in /tmp, /var/tmp, or other writable directories.Affected if Unexpected processes or files exist that correspond to attacker-executed commands
The environment is affected if FortiSandbox version is 4.0.0 through 4.0.4, 4.2.1 through 4.2.6, or 4.4.0 through 4.4.3 AND the HTTP management interface is accessible from untrusted networks.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.0.54.2.74.4.4
Upgrade FortiSandbox to vendor-provided patched version and implement proper input validation/sanitization on all parameters used in system calls.
FortiSandbox 4.0.5 (or later), 4.2.7 (or later), or 4.4.4 (or later) depending on your current branch
- Identify the current FortiSandbox version by checking the system information or running: diag system version
- Determine which version branch your current installation falls into (4.0.x, 4.2.x, or 4.4.x)
- For FortiSandbox 4.0.x versions: upgrade to version 4.0.5 or later
- For FortiSandbox 4.2.x versions: upgrade to version 4.2.7 or later
- For FortiSandbox 4.4.x versions: upgrade to version 4.4.4 or later
- Download the appropriate firmware from Fortinet's support portal (fortinet.com/support)
- Back up the current FortiSandbox configuration before upgrading
- Upload and install the firmware via FortiSandbox web UI or CLI console
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortisandbox
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,536.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21755 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-21755 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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