Local code execution via named-pipe path traversal
Published Apr 11, 2023 · Updated Oct 23, 2024
Relative path traversal in Fortinet FortiClient for Windows allows local users to execute unauthorized code via a named-pipe request. The named-pipe request handler fails to restrict attacker-controlled relative paths, allowing file creation outside its intended directory. A low-privileged local account must reach the pipe; successful exploitation permits code or command execution without user interaction.
Summary
What happened
Relative path traversal in Fortinet FortiClient for Windows allows local users to execute unauthorized code via a named-pipe request. The named-pipe request handler fails to restrict attacker-controlled relative paths, allowing file creation outside its intended directory. A low-privileged local account must reach the pipe; successful exploitation permits code or command execution without user interaction.
The record
- CVE
- CVE-2022-42470
- Published
- Apr 11, 2023
- Updated
- Oct 23, 2024
- Vendor
- Fortinet
- Product
- FortiClient for Windows
- Classifications
- CWE-23, CWE-22, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 11, 2023CVE publishedPublication date reported by the CVE source.
- Oct 23, 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=6.0.0 <=6.0.10
- Affected versionversion=6.2.0 <=6.2.9
- Affected versionversion=6.4.0 <=6.4.10
- Affected versionversion=7.0.0 <=7.0.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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