dbcve.org
ForticlientApplication · Fortinet

CVE-2024-40586

MEDIUM · 6.7 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 7.0.14 / 7.2.7 or later.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An Improper Access Control vulnerability [CWE-284] in FortiClient Windows version 7.4.0, version 7.2.6 and below, version 7.0.13 and below may allow a local user to escalate his privileges via FortiSSLVPNd service pipe.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A local privilege escalation vulnerability in FortiClient Windows versions 7.4.0, 7.2.6 and below, and 7.0.13 and below allows an authenticated local user to elevate privileges through improper access control on the FortiSSLVPNd service pipe.

MitigationUpgrade FortiClient to version 7.4.1, 7.2.7, or 7.0.14 or later to remediate the improper access control vulnerability on the FortiSSLVPNd service pipe.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ForticlientApplication
Affected:>= 7.0.3, < 7.0.14>= 7.2.0, < 7.2.7= 7.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify FortiClient installation
    Check if FortiClient is installed by looking in Program Files folder or querying the Windows registry under HKLM\SOFTWARE\Fortinet or checking Add/Remove Programs
    Affected if FortiClient is not installed on the system
  2. Check installed FortiClient version
    Open Programs and Features to view the FortiClient version, or run 'wmic product where "name like 'FortiClient%'" get name,version' in Command Prompt, then compare the version to the affected ranges: 7.0.3 through 7.0.13, 7.2.0 through 7.2.6, or exactly 7.4.0
    Affected if Installed version is 7.0.3 to 7.0.13, 7.2.0 to 7.2.6, or 7.4.0
  3. Confirm FortiSSLVPNd service presence
    Open Services console and look for FortiSSLVPNd service, or run 'sc query FortiSSLVPNd' in Command Prompt to check if the service exists on the system
    Affected if FortiSSLVPNd service is not present on the system
  4. Check FortiSSLVPNd service status
    Run 'sc query FortiSSLVPNd' or check the service status in Services console to see if the service is currently running
    Affected if FortiSSLVPNd service is running

User is affected if FortiClient version is 7.0.3-7.0.13, 7.2.0-7.2.6, or 7.4.0 AND the FortiSSLVPNd service is installed and running on the system

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.0.14 / 7.2.7 or later
Fixed in 7.0.147.2.7
Interim mitigation

Upgrade FortiClient to version 7.4.1, 7.2.7, or 7.0.14 or later to remediate the improper access control vulnerability on the FortiSSLVPNd service pipe.

Recommended fix High confidence

FortiClient 7.0.14+ (7.0.x branch), 7.2.7+ (7.2.x branch), or 7.4.1+ (7.4.x branch)

  1. Check current FortiClient version by opening FortiClient and navigating to Help > About, or by running 'forticlient --version' if CLI is available
  2. Download the fixed version from Fortinet's official support portal: FortiClient 7.0.14 or higher for 7.0.x users, FortiClient 7.2.7 or higher for 7.2.x users, or FortiClient 7.4.1 or higher for 7.4.x users
  3. Close FortiClient and any associated VPN processes before installation
  4. Run the installer with administrator privileges and follow the on-screen prompts to complete the update
  5. Restart the system if prompted and verify the new version is installed
Caveat Review Fortinet release notes for any changes to VPN configuration or compatibility requirements before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Forticlient Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-40586 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-40586 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data