Security readout for executives and security teams
Plain-English summary
FortiClient for Windows online installers 6.2.3 and below can load malicious DLL files from their own directory. An attacker already able to place files beside the installer could make code run when the installer executes. This is most relevant to shared download folders, software staging areas, or unmanaged installer copies.
Executive priority
Treat this as a targeted hygiene issue rather than an emergency. Prioritize environments using FortiClient deployment packages, shared software repositories, or unmanaged downloads because successful abuse can lead to local code execution.
Technical view
CVE-2020-9290 is an unsafe search path issue in FortiClientOnlineInstaller.exe and FortiClientVPNOnlineInstaller.exe for Windows 6.2.3 and below. The source states a local attacker controlling the installer directory may execute arbitrary code by placing malicious Filter Library DLL files there.
Likely exposure
Exposure is limited to Windows systems or deployment workflows that retain or run affected FortiClient online installers from directories writable by non-administrative users or attackers.
Exploitation context
The bundle does not report active exploitation, and CISA KEV status is false. The attacker needs local control over the installer’s directory, so this is not described as a remote network exploit.
Researcher notes
The available bundle gives affected versions and the unsafe DLL search-path condition, but no CVSS vector, CWE, exploit status, or specific fixed version. Avoid assuming broader FortiClient runtime exposure beyond the named online installers.
Mitigation direction
- Check Fortinet PSIRT FG-IR-19-060 for supported remediation guidance.
- Retire affected FortiClient online installers version 6.2.3 and below.
- Use only trusted Fortinet-sourced current installers for deployments.
- Store installers in access-controlled directories not writable by standard users.
- Review software distribution shares for stale affected installer copies.
Validation and detection
- Inventory FortiClientOnlineInstaller.exe and FortiClientVPNOnlineInstaller.exe across endpoints and deployment shares.
- Confirm discovered installer versions are not 6.2.3 or below.
- Check directory permissions where installers are stored or executed.
- Verify deployment tooling retrieves installers from trusted controlled locations.
- Look for historical execution of affected installers from user-writable paths.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-9290 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://fortiguard.com/psirt/FG-IR-19-060CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.