dbcve.org
FortisandboxApplication · Fortinet

CVE-2023-41682

HIGH · 7.5 CVSS v3.1 Published 2023-10-13
Fix available
A fix is available. Upgrade to after 4.2.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiSandbox 4.4.0, FortiSandbox 4.2.1 through 4.2.5, FortiSandbox 4.0.0 through 4.0.3, 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 allows attacker to denial of service via crafted http 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 confidence

FortiSandbox contains a path traversal vulnerability where crafted HTTP requests can escape the intended restricted directory, allowing attackers to access unauthorized files or cause denial of service. The vulnerability affects multiple legacy versions across the 2.x, 3.x, and 4.x product lines.

MitigationApply the vendor-supplied patch for your specific FortiSandbox version, or implement WAF rules to filter path traversal sequences (.., /, \) in HTTP requests as a compensating control until patching is feasible.

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
Affected:>= 2.4.0, <= 2.4.1>= 2.5.0, <= 2.5.2>= 3.2.0, <= 3.2.4>= 4.0.0, <= 4.0.3>= 4.2.0, <= 4.2.5= 4.4.0

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify FortiSandbox installation
    Locate FortiSandbox in your environment - this is typically a dedicated appliance or virtual machine running FortiSandbox software. Check your asset inventory or network scans for FortiSandbox devices.
    Affected if FortiSandbox is deployed in your environment
  2. Determine installed FortiSandbox version
    Access the FortiSandbox web UI or CLI and navigate to System > Settings > About, or run the command 'get system status' in the CLI to retrieve the firmware version.
    Affected if The installed version falls within any of these ranges: 2.4.0-2.4.1, 2.5.0-2.5.2, 3.2.0-3.2.4, 4.0.0-4.0.3, 4.2.0-4.2.5, or 4.4.0
  3. Verify HTTP service is accessible
    Confirm that the FortiSandbox web interface (HTTPS/HTTP) is accessible by attempting to reach the management IP or hostname on ports 80 or 443.
    Affected if The web interface is exposed and reachable from network segments where potential attackers exist
  4. Check for path traversal exposure
    Review any HTTP request logs, WAF logs, or IDS/IPS alerts for suspicious patterns containing '..' (double dots), encoded path sequences, or unusual directory traversal attempts targeting the FortiSandbox web service.

Your environment is affected if FortiSandbox is running and the installed version matches any of the listed vulnerable ranges (2.4.0-2.4.1, 2.5.0-2.5.2, 3.2.0-3.2.4, 4.0.0-4.0.3, 4.2.0-4.2.5, or 4.4.0) with the HTTP interface accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 4.2.5
Interim mitigation

Apply the vendor-supplied patch for your specific FortiSandbox version, or implement WAF rules to filter path traversal sequences (.., /, \) in HTTP requests as a compensating control until patching is feasible.

Recommended fix Moderate confidence

FortiSandbox 4.4.1 or later (check FortiGuard for exact fixed release)

  1. Check FortiGuard (https://www.fortiguard.com) for the official FortiSandbox firmware release notes and security advisories to confirm the fixed version
  2. Identify your current FortiSandbox version from the web UI or CLI: FortiSandbox > Dashboard > Status
  3. Download the recommended fixed firmware version from Fortinet Customer Support portal (https://support.fortinet.com)
  4. Review Fortinet's upgrade best practices documentation before proceeding
  5. Schedule a maintenance window as upgrades may require system downtime
  6. Backup the FortiSandbox configuration before upgrading
  7. Follow Fortinet's documented firmware upgrade procedure for FortiSandbox appliance
  8. After upgrade, verify the system is operational and the vulnerability is resolved by reviewing system logs
Caveat Review Fortinet release notes for any configuration or feature changes between your current version and the target fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortisandbox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-41682 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-41682 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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