dbcve.org
FortisandboxApplication · Fortinet

CVE-2020-29012

MEDIUM · 5.3 CVSS v3.1 Published 2021-09-08
Fix available
A fix is available. Upgrade to 3.2.2 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 insufficient session expiration vulnerability in FortiSandbox versions 3.2.1 and below may allow an attacker to reuse the unexpired admin user session IDs to gain information about other users configured on the device, should the attacker be able to obtain that session ID (via other, hypothetical attacks)

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

FortiSandbox versions 3.2.1 and below have insufficient session expiration, allowing admin session IDs to remain valid beyond acceptable timeframes. An attacker who obtains a valid session ID (through other attack vectors) can reuse it to access the device and retrieve information about other configured users.

MitigationUpgrade FortiSandbox to a version beyond 3.2.1 that includes the session expiration fix, or apply the relevant Fortinet patch. Additionally, enforce session timeout policies and rotate session IDs if possible.

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

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 installed FortiSandbox version
    Access the FortiSandbox GUI or CLI and retrieve the firmware version (typically via 'get system status' CLI command or System > Settings > Firmware in GUI)
    Affected if The installed version is 3.2.1 or lower, meaning it is before the 3.2.2 patch
  2. Confirm session expiration mechanism
    Locate the session timeout or idle timeout configuration for admin accounts in the FortiSandbox administrative settings
    Affected if No session timeout is configured or the configured timeout exceeds reasonable limits for administrative access
  3. Review active administrative sessions
    Use the FortiSandbox CLI or GUI to list currently active admin sessions (commonly via 'diagnose system session' or similar session management commands)
    Affected if Sessions persist beyond expected timeframes or there is no mechanism to force-expire idle sessions

The environment is affected if FortiSandbox version 3.2.1 or below is running AND there is no effective session expiration control limiting admin session validity.

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

Upgrade FortiSandbox to a version beyond 3.2.1 that includes the session expiration fix, or apply the relevant Fortinet patch. Additionally, enforce session timeout policies and rotate session IDs if possible.

Recommended fix High confidence

FortiSandbox 3.2.2 or later

  1. 1. Back up the current FortiSandbox configuration before initiating the upgrade
  2. 2. Download FortiSandbox version 3.2.2 or later from the Fortinet customer support portal
  3. 3. Upload the firmware upgrade file through the FortiSandbox administrative interface (System > Firmware) or via CLI
  4. 4. Reboot the device as prompted by the firmware upgrade process
  5. 5. After upgrade completes, verify the new version is running (System > Dashboard > Status)
  6. 6. Log out and log back in to establish a fresh session, confirming session management functions correctly
  7. 7. Verify session timeout settings are configured appropriately under Administration > Administrators
Caveat Standard firmware upgrade; review release notes for any configuration changes or migration requirements

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-29012 — 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-29012 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