dbcve.org
FortisandboxApplication · Fortinet

CVE-2022-27485

MEDIUM · 6.5 CVSS v3.1 Published 2023-04-11
Fix available
A fix is available. Upgrade to 3.2.4 / 4.0.3 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 neutralization of special elements used in an sql command ('sql injection') vulnerability [CWE-89] in Fortinet FortiSandbox version 4.2.0, 4.0.0 through 4.0.2, 3.2.0 through 3.2.3, 3.1.x and 3.0.x allows a remote and authenticated attacker with read permission to retrieve arbitrary files from the underlying Linux system via a crafted HTTP request.

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

SQL injection vulnerability in FortiSandbox allows an authenticated remote attacker with read-only permissions to retrieve arbitrary files from the underlying Linux filesystem via specially crafted HTTP requests containing malicious SQL payloads.

MitigationApply Fortinet's available patches for affected FortiSandbox versions (3.0.x, 3.1.x, 3.2.0-3.2.3, 4.0.0-4.0.2, 4.2.0). Restrict administrative access to trusted users only and minimize the attack surface by limiting HTTP/HTTPS exposure to internal networks.

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.0.1, <= 3.0.7>= 3.1.0, < 3.2.4>= 4.0.0, < 4.0.3= 4.2.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
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 installation and version
    Locate the FortiSandbox appliance or VM in your environment and determine the installed firmware version. This is typically visible in the web UI header, the CLI 'get system status' command, or the dashboard of the admin interface.
    Affected if The installed version falls within 3.0.1-3.0.7, 3.1.0-3.2.3, 4.0.0-4.0.2, or is exactly 4.2.0.
  2. Verify HTTP/HTTPS administrative interface is accessible
    Confirm that the FortiSandbox web administrative interface (TCP ports 80 or 443) is reachable from network locations where untrusted users could send HTTP requests.
    Affected if The administrative interface is exposed to networks accessible by users who are not fully trusted.
  3. Check for existing user accounts with read-only privileges
    Review the FortiSandbox user database, typically found under System > Admin > Administrators in the web UI or via 'show system admin' CLI command, to identify accounts with read-only or limited permissions.
    Affected if There are any read-only or limited-privilege user accounts configured that could be compromised.
  4. Examine logs for suspicious SQL injection patterns
    Search FortiSandbox logs (via Log & Report > Event Log in the web UI or 'execute log-viewer' CLI) for HTTP requests containing SQL keywords (SELECT, UNION, INSERT) or unusual database-like syntax in URL parameters.
    Affected if Recent logs show SQL injection attempts or unusual database query patterns in HTTP request parameters.

You are affected if FortiSandbox is running a version within the affected ranges AND the administrative web interface is accessible to an attacker who could obtain valid read-only credentials.

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 3.2.4 / 4.0.3 or later
Fixed in 3.2.44.0.3
Interim mitigation

Apply Fortinet's available patches for affected FortiSandbox versions (3.0.x, 3.1.x, 3.2.0-3.2.3, 4.0.0-4.0.2, 4.2.0). Restrict administrative access to trusted users only and minimize the attack surface by limiting HTTP/HTTPS exposure to internal networks.

Recommended fix High confidence

FortiSandbox 4.2.1 or later (or 4.0.3+ for 4.0.x, 3.2.4+ for 3.1.x, 3.0.8+ for 3.0.x)

  1. 1. Identify the current FortiSandbox version by navigating to Dashboard > Status in the web UI or running 'get system status' in the CLI
  2. 2. Determine the appropriate upgrade path based on current version: if on 3.0.x, upgrade to 3.0.8 or later (recommended: 3.2.4+ or 4.0.3+); if on 3.1.x, upgrade to 3.2.4 or later; if on 4.0.0-4.0.2, upgrade to 4.0.3 or later; if on 4.2.0, upgrade to 4.2.1 or later
  3. 3. Back up the FortiSandbox configuration via System > Maintenance > Backup & Restore in the web UI
  4. 4. Download the firmware from Fortinet Customer Support portal (https://support.fortinet.com/) for the target fixed version
  5. 5. Upload and install the firmware via System > Maintenance > Firmware in the web UI, or via 'execute firmware upload' in the CLI
  6. 6. After upgrade, verify the system is operational and confirm the version via 'get system status'
  7. 7. Validate that the SQL injection vulnerability is no longer present by confirming the version is at or above the fixed release for your branch
Caveat Review Fortinet release notes for the target version for any configuration or behavioral changes; firmware upgrades may require downtime and should be tested in a staging environment first

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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