FortisandboxApplication · Fortinet
CVE-2021-24010
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 · uneditedImproper limitation of a pathname to a restricted directory vulnerabilities in FortiSandbox 3.2.0 through 3.2.2, and 3.1.0 through 3.1.4 may allow an authenticated user to obtain unauthorized access to files and data via specifially crafted web 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 confidenceThis is a path traversal vulnerability in FortiSandbox's web interface. An authenticated attacker can craft malicious web requests containing directory traversal sequences (e.g., ../../../) to escape the restricted directory and access sensitive files outside the intended scope.
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
>= 3.1.0, < 3.1.5>= 3.2.0, < 3.2.3CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Check FortiSandbox firmware versionLog into the FortiSandbox CLI and run the command: get system status. Alternatively, in the web UI, go to Dashboard > System Information > Firmware Version.Affected if The installed version falls within >= 3.1.0 and < 3.1.5, or >= 3.2.0 and < 3.2.3.
-
Verify web interface is enabledIn the FortiSandbox CLI, run: show system interface. Check for HTTPS or HTTP admin access configuration. In the web UI, navigate to System > Network > Interface and confirm the administrative access includes HTTPS or HTTP.Affected if The web interface (HTTPS or HTTP) is enabled and reachable on any interface.
-
Confirm authentication is possibleAttempt to log into the FortiSandbox web interface with valid admin credentials, or verify that local user accounts exist via: diagnose system admin list in the CLI.Affected if An authenticated user account exists with access to the web interface.
-
Review access logs for path traversal patternsIn the web UI, go to Log & Report > Event Logs > System Events. Search for HTTP requests containing patterns such as ../, ..%2f, or multiple forward slashes in URI paths. Alternatively, use the CLI: execute log filter category 1 and review logs for suspicious URL patterns.Affected if Any HTTP requests containing directory traversal sequences (e.g., ../../../) are present in the logs.
A system is affected if it runs FortiSandbox firmware version 3.1.0 through 3.1.4 or 3.2.0 through 3.2.2, has the web interface enabled, and has an authenticated user capable of sending web requests.
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.
From vendor data3.1.53.2.3
Upgrade FortiSandbox to version 3.2.3 or later (for 3.2.x) or 3.1.5 or later (for 3.1.x). If immediate patching is not possible, restrict web interface access to trusted IP addresses and monitor for suspicious path traversal patterns in HTTP requests.
Fix this in Fortisandbox
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-24010 — 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-2021-24010 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