Skip to main content
Vulnerability Database/CVE-2024-36513

CVE-2024-36513: Fortinet FortiClient Privilege Escalation

CVE-2024-36513 is a privilege escalation vulnerability in Fortinet FortiClient for Windows that allows authenticated users to elevate privileges via lua auto patch scripts. This article covers technical details, affected versions, security impact, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2024-36513 Overview

CVE-2024-36513 is a privilege context switching vulnerability [CWE-270] affecting FortiClient for Windows. The flaw allows an authenticated local user to escalate privileges through Lua auto patch scripts executed by the client. Fortinet published the advisory on November 12, 2024.

The vulnerability affects FortiClient Windows version 7.2.4 and below, 7.0.12 and below, and all 6.4 versions. Successful exploitation grants an attacker elevated privileges on the host, leading to full compromise of confidentiality, integrity, and availability on the local system.

Critical Impact

Authenticated local attackers can abuse Lua auto patch scripts in FortiClient Windows to escalate privileges and gain SYSTEM-level control of the endpoint.

Affected Products

  • FortiClient for Windows 7.2.0 through 7.2.4
  • FortiClient for Windows 7.0.0 through 7.0.12
  • FortiClient for Windows 6.4 (all versions)

Discovery Timeline

  • 2024-11-12 - CVE-2024-36513 published to NVD and Fortinet advisory FG-IR-24-144 released
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2024-36513

Vulnerability Analysis

FortiClient for Windows uses Lua scripts to orchestrate automatic patching of client components. These scripts execute in a privileged context tied to the FortiClient service, which runs with SYSTEM-level rights. The vulnerability arises when the client fails to correctly separate the privilege context of the script runtime from the invoking user session.

An authenticated local user can influence the script execution path or input to trigger operations in the higher-privileged context. This produces a vertical Privilege Escalation on the local host. The issue is categorized under Improper Privilege Management [CWE-270].

The attack requires local access and low privileges, but no user interaction. Because the vulnerability crosses a privilege boundary, exploitation changes the security scope and yields high impact on confidentiality, integrity, and availability.

Root Cause

The root cause is a privilege context switching error in how the FortiClient auto patch subsystem invokes Lua scripts. The service does not properly drop or isolate privileges before processing user-controllable inputs. Operations intended to run on behalf of a limited user instead execute with the service account's elevated rights.

Attack Vector

Exploitation requires an authenticated local user on a vulnerable FortiClient Windows host. The attacker interacts with the auto patch mechanism to coerce Lua script execution that performs privileged file or process operations. No remote network access and no user interaction from a second user are required.

No public proof-of-concept exploit is listed in Exploit-DB, and the CVE is not present on the CISA Known Exploited Vulnerabilities catalog. The EPSS probability remains low at the time of writing, but local Privilege Escalation flaws in endpoint security products are frequently incorporated into post-exploitation toolkits.

See the FortiGuard advisory FG-IR-24-144 for vendor technical details.

Detection Methods for CVE-2024-36513

Indicators of Compromise

  • Unexpected child processes spawned by the FortiClient service (FortiClient.exe, FortiESNAC.exe, or related binaries) running as SYSTEM.
  • Lua script files or interpreter artifacts written to FortiClient installation directories by non-administrative users.
  • New or modified files under C:\Program Files\Fortinet\FortiClient\ originating from a non-SYSTEM user context.
  • Local account activity immediately followed by SYSTEM-level process creation on the same host.

Detection Strategies

  • Hunt for process-creation events where a FortiClient service process launches cmd.exe, powershell.exe, or script interpreters.
  • Correlate file-write events in FortiClient directories with the originating user token to flag privilege boundary crossings.
  • Alert on local token elevation events (Windows Event ID 4672) tied to accounts that should not routinely gain SeDebugPrivilege or SeTcbPrivilege.

Monitoring Recommendations

  • Enable Windows command-line auditing and PowerShell script block logging on all endpoints running FortiClient.
  • Forward endpoint process, file, and registry telemetry to a centralized data lake for retrospective hunting against the Lua auto patch flow.
  • Track FortiClient version inventory continuously to identify hosts still running affected 7.2.x, 7.0.x, or 6.4 builds.

How to Mitigate CVE-2024-36513

Immediate Actions Required

  • Inventory all Windows endpoints running FortiClient and identify versions at or below 7.2.4, 7.0.12, and any 6.4 build.
  • Upgrade affected hosts to FortiClient Windows 7.2.5 or later, or 7.0.13 or later, per the Fortinet advisory.
  • Migrate off the 6.4 branch, which remains vulnerable across all versions and should be replaced with a fixed release.
  • Restrict local interactive logon on sensitive hosts to reduce the pool of accounts able to trigger the flaw.

Patch Information

Fortinet published fixes in FortiClient Windows 7.2.5 and 7.0.13. Users of the 6.4 branch must upgrade to a supported, patched release. Full remediation guidance is available in FortiGuard advisory FG-IR-24-144.

Workarounds

  • No official workaround is documented by Fortinet. Patching is the required remediation.
  • As a compensating control, enforce application control policies that restrict script interpreters from executing within FortiClient service contexts.
  • Limit local administrative and standard user access on servers and shared workstations until patching is complete.
bash
# Verify installed FortiClient version on Windows
wmic product where "Name like 'FortiClient%'" get Name,Version

# PowerShell alternative
Get-CimInstance -ClassName Win32_Product | Where-Object { $_.Name -like 'FortiClient*' } | Select-Object Name, Version

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.