Local privilege escalation via symlinked temp files
Published Jun 1, 2020 · Updated Oct 25, 2024
Insecure temporary file handling in FortiClient for Windows 6.2.1 and earlier allows local users to gain elevated privileges via a symlink attack. The client exhausts predictable temporary-file names, then follows an attacker-created symbolic link when creating a privileged file. A local user account is required, and successful exploitation can compromise confidentiality, integrity, and availability through elevated privileges.
Summary
What happened
Insecure temporary file handling in FortiClient for Windows 6.2.1 and earlier allows local users to gain elevated privileges via a symlink attack. The client exhausts predictable temporary-file names, then follows an attacker-created symbolic link when creating a privileged file. A local user account is required, and successful exploitation can compromise confidentiality, integrity, and availability through elevated privileges.
The record
- CVE
- CVE-2020-9291
- Published
- Jun 1, 2020
- Updated
- Oct 25, 2024
- Vendor
- Fortinet
- Product
- FortiClient for Windows
- Classifications
- CWE-668, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 1, 2020CVE publishedPublication date reported by the CVE source.
- Oct 25, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=FortiClient for Windows 6.2.1 and earlier and FortiClient for Windows 6.0.9 and earlier
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo