dbcve.org
FortisandboxApplication · Fortinet

CVE-2024-31490

MEDIUM · 6.5 CVSS v3.1 Published 2024-09-10
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
An exposure of sensitive information to an unauthorized actor 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.2 through 3.2.4, FortiSandbox 3.1.5 allows attacker to information disclosure via HTTP get 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

This is an information disclosure vulnerability in Fortinet FortiSandbox that allows unauthorized actors to access sensitive information via specially crafted HTTP GET requests. The vulnerability affects multiple version branches (3.1.5, 3.2.2-3.2.4, 4.0 all versions, 4.2.1-4.2.6, and 4.4.0-4.4.4) and enables exposure of sensitive data without authentication.

MitigationApply the vendor-supplied patch or upgrade to a FortiSandbox version beyond 4.4.4 (for 4.x branches) or beyond 4.2.6 (for 4.2.x branch), and beyond 3.2.4/3.1.5 for older branches. Verify the upgrade resolves the vector and test system functionality post-upgrade.

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:>= 3.2.2, < 4.2.7>= 4.4.0, < 4.4.5= 3.1.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 if FortiSandbox is present
    Check for FortiSandbox processes or services running on the system, or look for FortiSandbox-related network services listening on ports (typically 443 or 8443 for the web interface)
    Affected if FortiSandbox software is installed and running on the system
  2. Determine the installed FortiSandbox version
    Access the FortiSandbox web interface or CLI and retrieve the firmware/software version information. This is typically found in the System > Settings or About section of the GUI, or via 'get system status' command in CLI
    Affected if The installed version falls within 3.1.5, 3.2.2-3.2.4, 4.0.x, 4.2.1-4.2.6, or 4.4.0-4.4.4
  3. Verify HTTP interface exposure
    Determine if the FortiSandbox web interface (HTTP/HTTPS service) is accessible from network locations where unauthorized actors could send requests. Check firewall rules and interface bindings
    Affected if The HTTP/HTTPS interface is exposed to untrusted networks or the internet without proper access controls
  4. Review HTTP access logs for suspicious requests
    Examine FortiSandbox HTTP server logs for unusual or crafted GET requests, especially those that may be attempting to access sensitive data endpoints without proper authentication
    Affected if There are log entries showing unauthenticated HTTP GET requests to sensitive endpoints, particularly from untrusted sources

You are affected if FortiSandbox is running a version within 3.1.5, 3.2.2-3.2.4, 4.0.x, 4.2.1-4.2.6, or 4.4.0-4.4.4 AND the HTTP interface is accessible to unauthorized actors.

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

Apply the vendor-supplied patch or upgrade to a FortiSandbox version beyond 4.4.4 (for 4.x branches) or beyond 4.2.6 (for 4.2.x branch), and beyond 3.2.4/3.1.5 for older branches. Verify the upgrade resolves the vector and test system functionality post-upgrade.

Recommended fix Moderate confidence

Upgrade to FortiSandbox 4.4.5 (for 4.4.x branch) or 4.2.7 (for 4.2.x branch). For older branches (4.0.x, 3.2.x, 3.1.x), upgrade to the latest 4.4.x branch (4.4.5 or later)

  1. 1. Identify the current FortiSandbox version by navigating to Dashboard > Status or using the CLI command 'get system status'
  2. 2. Based on current version, determine the appropriate upgrade path to a fixed release
  3. 3. Download the fixed firmware from Fortinet customer support portal or FortiGuard
  4. 4. Backup the current FortiSandbox configuration
  5. 5. Upload and install the firmware via System > Firmware or via CLI with 'execute firmware upgrade'
  6. 6. After upgrade, verify the version and confirm the vulnerability is resolved by reviewing system logs
Caveat Upgrading across major version branches may require configuration review; ensure compatibility with integrated systems and review Fortinet upgrade notes

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
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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