FortisandboxApplication · Fortinet
CVE-2023-47541
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 · uneditedAn improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiSandbox 4.4.0 through 4.4.2, FortiSandbox 4.2.1 through 4.2.6, FortiSandbox 4.0 all versions, FortiSandbox 3.2 all versions, FortiSandbox 3.1 all versions, FortiSandbox 3.0 all versions, FortiSandbox 2.5 all versions, FortiSandbox 2.4 all versions, FortiSandbox 2.3 all versions, FortiSandbox 2.2 all versions, FortiSandbox 2.1 all versions, FortiSandbox 2.0 all versions allows attacker to execute unauthorized code or commands via CLI.
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 confidenceA path traversal vulnerability in FortiSandbox allows authenticated attackers to escape restricted directories and execute unauthorized code or commands through the CLI interface. The improper limitation of pathname to a restricted directory enables traversal using special characters in file paths.
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
>= 2.0.0, < 4.2.7>= 4.4.0, < 4.4.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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 firmware versionAccess the CLI and run 'get system status' command, or check the GUI under System > Status to retrieve the firmware version numberAffected if Version is 2.0.0 through 4.2.6, or 4.4.0 through 4.2.2 (vulnerable ranges)
-
Confirm CLI access is enabledReview admin access settings by running 'show system accprofile' and checking if CLI access (SSH or console) is permitted for any admin profilesAffected if CLI interface is accessible to authenticated users or administrators
The system is affected only if the installed FortiSandbox version falls within 2.0.0-4.2.6 or 4.4.0-4.2.2 AND authenticated CLI access is available.
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.2.74.4.3
Apply the vendor-supplied patches for all affected FortiSandbox versions. Upgrade to FortiSandbox 4.4.3 or later, or 4.2.7 or later, as appropriate for your deployment.
FortiSandbox 4.2.7 or 4.4.3 (depending on which branch you're on)
- 1. Identify the current FortiSandbox version by accessing the FortiGuard portal or checking system information
- 2. If running FortiSandbox 4.4.0-4.4.2, upgrade to version 4.4.3 or later
- 3. If running FortiSandbox 4.2.1-4.2.6, upgrade to version 4.2.7 or later
- 4. For older versions (2.0-4.0.x series), upgrade to one of the fixed versions (4.2.7 or 4.4.3) as per Fortinet's migration guidance
- 5. After upgrade, verify the system is operational and review CLI access controls
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortisandbox
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47541 — 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-2023-47541 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