CVE-2022-40681

7.1 HIGH

📋 TL;DR

This vulnerability in Fortinet FortiClient for Windows allows attackers to cause denial of service by sending specially crafted requests to a specific named pipe. The flaw stems from incorrect authorization checks, enabling disruption of FortiClient functionality. Organizations using affected FortiClient versions on Windows systems are at risk.

💻 Affected Systems

Products:
  • Fortinet FortiClient
Versions: 7.0.0 - 7.0.7, 6.4.0 - 6.4.9, 6.2.0 - 6.2.9, 6.0.0 - 6.0.10
Operating Systems: Windows
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects Windows versions of FortiClient. Named pipe access typically requires some level of system access.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete disruption of FortiClient functionality, potentially affecting VPN connectivity, endpoint protection, and security posture monitoring on affected systems.

🟠

Likely Case

Temporary denial of service affecting FortiClient services, requiring service restart or system reboot to restore functionality.

🟢

If Mitigated

Minimal impact with proper network segmentation and access controls limiting named pipe exposure to untrusted users.

🌐 Internet-Facing: LOW - Exploitation requires local system access or ability to communicate with named pipes, which are typically not internet-exposed.
🏢 Internal Only: MEDIUM - Malicious insiders or compromised internal systems could exploit this to disrupt FortiClient on targeted workstations.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires ability to send crafted requests to the specific named pipe, which typically requires some level of system access. No public exploit code has been disclosed.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: FortiClient 7.0.8, 6.4.10, 6.2.10, 6.0.11 and later

Vendor Advisory: https://fortiguard.com/psirt/FG-IR-22-299

Restart Required: Yes

Instructions:

1. Download latest FortiClient version from Fortinet support portal. 2. Uninstall current FortiClient. 3. Install updated version. 4. Restart system to ensure all services are properly updated.

🔧 Temporary Workarounds

Restrict Named Pipe Access

windows

Configure Windows security settings to restrict access to the vulnerable named pipe to only trusted users and processes.

Use Windows Security Policy or PowerShell to modify named pipe permissions: Get-Acl \\.\pipe\forticlient_pipe | Set-Acl -Path \\.\pipe\forticlient_pipe

Network Segmentation

all

Implement network segmentation to limit which systems can communicate with FortiClient endpoints.

🧯 If You Can't Patch

  • Implement strict access controls to limit which users and processes can interact with named pipes on affected systems.
  • Monitor for unusual named pipe access attempts and implement additional endpoint security controls.

🔍 How to Verify

Check if Vulnerable:

Check FortiClient version in About section or via command: "FortiClient.exe --version" and compare against affected versions.

Check Version:

FortiClient.exe --version

Verify Fix Applied:

Verify installed version is 7.0.8+, 6.4.10+, 6.2.10+, or 6.0.11+ and test FortiClient functionality remains stable during normal operations.

📡 Detection & Monitoring

Log Indicators:

  • Windows Event Logs showing access denied errors for named pipe operations
  • FortiClient service crash or restart events
  • Unusual named pipe connection attempts

Network Indicators:

  • Multiple connection attempts to named pipes from unexpected sources
  • Unusual inter-process communication patterns

SIEM Query:

EventID=4688 OR EventID=4663 AND ProcessName="FortiClient.exe" AND ObjectType="File" AND ObjectName LIKE "%pipe%forticlient%"

🔗 References

📤 Share & Export