dbcve.org
FortisandboxApplication · Fortinet

CVE-2020-29011

HIGH · 8.8 CVSS v3.1 Published 2021-08-04
Fix available
A fix is available. Upgrade to 3.1.5 / 3.2.2 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Instances of SQL Injection vulnerabilities in the checksum search and MTA-quarantine modules of FortiSandbox 3.2.0 through 3.2.2, and 3.1.0 through 3.1.4 may allow an authenticated attacker to execute unauthorized code on the underlying SQL interpreter via specifically 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

SQL injection vulnerabilities in the checksum search and MTA-quarantine modules of FortiSandbox allow authenticated attackers to execute arbitrary code on the underlying SQL database via crafted HTTP requests. The vulnerability affects versions 3.1.0-3.1.4 and 3.2.0-3.2.2.

MitigationUpgrade FortiSandbox to a patched version beyond 3.2.2. If immediate patching is not possible, restrict administrative access to trusted IPs and monitor for suspicious SQL-like patterns in HTTP requests to the affected modules.

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.1.5>= 3.2.0, < 3.2.2

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Check FortiSandbox version
    Run command: fortiSandbox -v or access Web UI > System > FortiSandbox > About to view the installed version number
    Affected if Version is 3.1.0-3.1.4 or 3.2.0-3.2.2 (versions before 3.1.5 or 3.2.2 are vulnerable)
  2. Verify administrative access exists
    Check for valid administrator accounts configured in FortiSandbox via Web UI > System > Administrators or CLI command: get system admin
    Affected if Any authenticated administrator account exists, as attackers need valid credentials to exploit the SQL injection
  3. Identify access to checksum search module
    Check if the checksum search feature is enabled and accessible at /ajax/checksum/search or similar endpoint; review Web UI for Job View > Checksum Search visibility
    Affected if Checksum search module is enabled and accessible without additional network restrictions
  4. Identify access to MTA-quarantine module
    Review Web UI for MTA (Mail Transfer Agent) quarantine functionality accessible via Email > Quarantine or similar path
    Affected if MTA-quarantine module is enabled and accessible on the FortiSandbox device

User is affected if FortiSandbox version is 3.1.0-3.1.4 or 3.2.0-3.2.2 AND either the checksum search or MTA-quarantine module is accessible to authenticated administrators.

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.1.5 / 3.2.2 or later
Fixed in 3.1.53.2.2
Interim mitigation

Upgrade FortiSandbox to a patched version beyond 3.2.2. If immediate patching is not possible, restrict administrative access to trusted IPs and monitor for suspicious SQL-like patterns in HTTP requests to the affected modules.

Recommended fix High confidence

FortiSandbox 3.1.5 or later (3.1.x branch); FortiSandbox 3.2.2 or later (3.2.x branch). Recommend latest stable 3.1.x or 3.2.x release available from Fortiguard.

  1. 1. Identify the current FortiSandbox version by accessing the device GUI or CLI
  2. 2. If running version 3.1.x: Plan upgrade to version 3.1.5 or later (preferably latest 3.1.x stable release)
  3. 3. If running version 3.2.0 or 3.2.1: Plan upgrade to version 3.2.2 or later (preferably latest 3.2.x stable release)
  4. 4. Review FortiGuard release notes for upgrade procedures and any special migration requirements
  5. 5. Back up the current FortiSandbox configuration before proceeding
  6. 6. Perform the upgrade via FortiSandbox GUI (System > Settings > Firmware) or CLI using the firmware upgrade command
  7. 7. After upgrade, verify the new version is running and confirm the SQL injection vulnerability is resolved
  8. 8. Validate that all expected functionality (checksum search, MTA-quarantine) operates correctly post-upgrade
Caveat Review release notes for any compatibility changes between 3.1.x and 3.2.x branches; consider testing in non-production 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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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