LiveActive security incident?Get immediate response
CVE Record

CVE-2020-29011: Instances of SQL Injection vulnerabilities in the checksum search and MTA-quarantine modules of FortiSandbo...

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.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-29011 is a high-severity SQL injection issue in Fortinet FortiSandbox. An authenticated user could send crafted HTTP requests to affected modules and make the database interpreter run unintended SQL. For executives, the main concern is compromise of a security appliance that may process sensitive files and threat data.

Executive priority

Treat as priority remediation for any affected FortiSandbox deployment. The appliance role and high CIA impact justify prompt action, especially where many users can authenticate or management access is broadly reachable.

Technical view

The issue affects FortiSandbox 3.2.0 through 3.2.2 and 3.1.0 through 3.1.4. The vulnerable areas are the checksum search and MTA-quarantine modules. CVSS 3.1 is 8.8 with network access, low attack complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to organizations running the listed FortiSandbox versions with authenticated users able to reach the affected web functions over the network.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The CVSS temporal vector includes E:F, but no public exploit details or exploitation campaign evidence are provided here.

Researcher notes

Evidence is clear on affected versions, vulnerable modules, authentication requirement, and impact scoring. The bundle does not provide payload details, patch version names, CWE mapping, or confirmed in-the-wild exploitation.

Mitigation direction

  • Review Fortinet advisory FG-IR-20-171 for fixed releases and vendor workarounds.
  • Upgrade affected FortiSandbox deployments according to Fortinet guidance.
  • Restrict FortiSandbox access to trusted administrative networks and users.
  • Review and reduce unnecessary authenticated accounts on FortiSandbox.

Validation and detection

  • Inventory FortiSandbox versions across all environments.
  • Confirm whether any instance runs 3.2.0-3.2.2 or 3.1.0-3.1.4.
  • Review Fortinet guidance for the corrected version path.
  • Check access logs for unusual authenticated use of the affected modules.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-29011 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:X/RC:X

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:X/RC:X2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2020-29011Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:X/RC:X

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
FortinetFortinet FortiSandboxFortiSandbox 3.2.2, 3.2.1, 3.2.0, 3.1.4, 3.1.3, 3.1.2, 3.1.1, 3.1.0Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.