LiveActive security incident?Get immediate response
CVE Record

CVE-2020-29014: A concurrent execution using shared resource with improper synchronization ('race condition') in the comman...

A concurrent execution using shared resource with improper synchronization ('race condition') in the command shell of FortiSandbox before 3.2.2 may allow an authenticated attacker to bring the system into an unresponsive state via specifically orchestrated sequences of commands.

MediumCVSS 6.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

FortiSandbox versions before 3.2.2 have a race-condition flaw in the command shell. An authenticated attacker could make the appliance unresponsive by issuing carefully timed command sequences. This is mainly an availability risk, with limited confidentiality and integrity impact noted in CVSS.

Executive priority

Treat this as a moderate operational resilience issue. It can disrupt a FortiSandbox appliance but requires authenticated access. Prioritize remediation for internet-adjacent, shared-administration, or business-critical malware analysis environments.

Technical view

CVE-2020-29014 is an improper synchronization race condition in Fortinet FortiSandbox command shell before 3.2.2. The CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L, meaning network access and low privileges are enough, with no user interaction required.

Likely exposure

Exposure is limited to Fortinet FortiSandbox deployments running versions before 3.2.2. Risk is higher where authenticated shell access is broadly available, poorly monitored, or reachable from less-trusted networks.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation evidence. The issue requires authentication and specific command sequencing, so it is less likely to be mass-exploited than unauthenticated edge-device flaws.

Researcher notes

The bundle identifies no CWE entry and provides no exploit details beyond authenticated command sequencing. Analysis should stay focused on version exposure, privilege boundaries, shell access paths, and availability impact. Do not assume unauthenticated exploitation or confirmed in-the-wild use.

Mitigation direction

  • Inventory FortiSandbox appliances and identify versions before 3.2.2.
  • Review Fortinet advisory FG-IR-20-185 for fixed-release guidance.
  • Upgrade affected FortiSandbox systems to 3.2.2 or later where applicable.
  • Restrict command shell access to trusted administrators only.
  • Monitor FortiSandbox availability and administrative shell activity.

Validation and detection

  • Confirm each FortiSandbox version from administrative inventory or device management records.
  • Check whether any appliance is running a version before 3.2.2.
  • Review administrator and shell-access logs for unusual command activity.
  • Verify access controls limit shell access to required personnel.
  • Confirm vendor advisory guidance has been applied to affected systems.
Prepared
Confidence
high
Sources
3

Public sources used

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.

cve · low confidence lookup

CVE-2020-29014 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
Medium
CVSS
6.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:X/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
6.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:X/RL:X/RC:X2.83.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.3Medium
CVSS 3.1 vector shape for CVE-2020-29014Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:X/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 before 3.2.2Listed
Weakness

CWE details

No CWE listed

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