dbcve.org
FortisandboxApplication · Fortinet

CVE-2024-31487

MEDIUM · 6.5 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 4.2.7 / 4.4.5 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 through 4.4.4, 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 allows attacker to information disclosure 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 · moderate confidence

FortiSandbox contains a path traversal vulnerability in its web interface that allows attackers to craft HTTP requests with directory traversal sequences (e.g., ../) to access sensitive files outside the intended web root directory, leading to unauthorized information disclosure.

MitigationUpgrade FortiSandbox to the latest version to obtain the patch. As immediate mitigation, restrict access to the administrative interface to trusted IP addresses using firewall rules or access lists.

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, < 4.2.7>= 4.4.0, < 4.4.5

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
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 checks

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

  1. Identify FortiSandbox installed version
    Log into the FortiSandbox CLI or GUI and navigate to the Dashboard or System > Settings page to view the firmware version. Alternatively, use the command: get system status
    Affected if The displayed version falls within 2.4.0 to 4.2.6, or 4.4.0 to 4.4.4
  2. Confirm web interface is enabled
    Check System > Settings in the GUI or run: get system interface to verify that the administrative web interface (HTTPS/HTTP) is enabled on the management interface
    Affected if The web interface is enabled and accessible
  3. Verify network accessibility of admin interface
    Determine if the management interface IP is reachable from untrusted networks. Check firewall policies or run: diagnose system interface to see which interfaces have HTTPS/HTTP services enabled
    Affected if The administrative web interface is exposed to untrusted or external networks

You are affected if your FortiSandbox version is 2.4.0 through 4.2.6 or 4.4.0 through 4.4.4 AND the web interface is enabled and accessible from a network where untrusted users could send HTTP requests.

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 4.2.7 / 4.4.5 or later
Fixed in 4.2.74.4.5
Interim mitigation

Upgrade FortiSandbox to the latest version to obtain the patch. As immediate mitigation, restrict access to the administrative interface to trusted IP addresses using firewall rules or access lists.

Recommended fix High confidence

FortiSandbox 4.2.7 or later, or 4.4.5 or later (depending on branch)

  1. 1. Identify the currently installed FortiSandbox version via the web UI (System > Dashboard > Status) or CLI: 'get system status'
  2. 2. If running version 4.2.x (between 4.2.1 and 4.2.6), plan upgrade to version 4.2.7 or later
  3. 3. If running version 4.4.x (between 4.4.0 and 4.4.4), plan upgrade to version 4.4.5 or later
  4. 4. For versions 4.0.x, 3.2.x, 3.1.x, 3.0.x, 2.5.x, and 2.4.x, note these are end-of-life and no patches are available; migration to a supported version (4.2.7+ or 4.4.5+) is required
  5. 5. Before upgrading, backup the FortiSandbox configuration via the web UI (System > Maintenance > Backup & Restore) or CLI: 'execute backup full-config'
  6. 6. Download the firmware upgrade from Fortinet Customer Support portal or FortiGuard
  7. 7. Upload and install the new firmware via System > Firmware or via CLI: 'execute system firmware-upgrade <image_file> tftp/ftp/scp
  8. 8. After reboot, verify the new version and confirm the vulnerability is resolved
Caveat Firmware upgrades may require downtime; verify compatibility with other Fortinet products in your environment; older branches (4.0, 3.x, 2.x) are end-of-life and require migration to supported branches

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

Fix this in Fortisandbox Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
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,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-31487 — 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-2024-31487 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