LiveActive security incident?Get immediate response
CVE Record

CVE-2021-24010: Improper limitation of a pathname to a restricted directory vulnerabilities in FortiSandbox 3.2.0 through 3...

Improper limitation of a pathname to a restricted directory vulnerabilities in FortiSandbox 3.2.0 through 3.2.2, and 3.1.0 through 3.1.4 may allow an authenticated user to obtain unauthorized access to files and data via specifially crafted web requests.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

FortiSandbox versions 3.1.0 through 3.1.4 and 3.2.0 through 3.2.2 have a path restriction flaw. An authenticated user could make crafted web requests to access unauthorized files or data. The main business risk is sensitive data exposure and possible tampering by someone with valid low-level access.

Executive priority

Prioritize remediation for internet-reachable or broadly accessible FortiSandbox systems. The flaw requires authentication, but low privileges are enough, and the confidentiality and integrity impacts are high. Schedule upgrade or vendor-guided mitigation promptly.

Technical view

CVE-2021-24010 is an improper pathname limitation issue in Fortinet FortiSandbox. CVSS 3.1 is 8.1 with network access, low complexity, low privileges, no user interaction, high confidentiality impact, high integrity impact, and no availability impact. The provided sources do not list CWE details or fixed versions.

Likely exposure

Exposure is limited to organizations running FortiSandbox 3.1.0-3.1.4 or 3.2.0-3.2.2 with authenticated users able to reach the web interface.

Exploitation context

The CVE is not listed as KEV in the supplied bundle. The CVSS vector marks exploit code maturity as functional, but the provided sources do not prove active exploitation. Treat this as a serious authenticated-access risk, not confirmed in-the-wild exploitation.

Researcher notes

The public bundle supports an authenticated path traversal-style file access issue through crafted web requests. Evidence is incomplete on fixed versions, CWE mapping, and observed exploitation. Validation should focus on version confirmation, management-plane exposure, account scope, and Fortinet advisory alignment.

Mitigation direction

  • Review Fortinet advisory FG-IR-20-202 for fixed releases or vendor-approved mitigations.
  • Upgrade affected FortiSandbox appliances once the vendor identifies a fixed version.
  • Restrict FortiSandbox web management access to trusted administrative networks.
  • Audit FortiSandbox accounts and remove unnecessary access.
  • Monitor for unusual authenticated web requests and file-access anomalies.

Validation and detection

  • Inventory FortiSandbox appliances and confirm exact software versions.
  • Check whether versions match 3.1.0-3.1.4 or 3.2.0-3.2.2.
  • Confirm the web interface is not broadly reachable.
  • Review user accounts with FortiSandbox access for least privilege.
  • Check logs for suspicious authenticated requests or unauthorized file access indicators.
Prepared
Confidence
medium
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.

cve · low confidence lookup

CVE-2021-24010 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.1 (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:N/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.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N/E:F/RL:X/RC:X2.85.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2021-24010Attack 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:N/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.