dbcve.org
ForticlientApplication · Fortinet

CVE-2024-47574

HIGH · 7.8 CVSS v3.1 Published 2024-11-13
Fix available
A fix is available. Upgrade to 7.0.13 / 7.2.5 or later.
See remediation →
80/100
Remediation priority · High
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
A authentication bypass using an alternate path or channel in Fortinet FortiClientWindows version 7.4.0, versions 7.2.4 through 7.2.0, versions 7.0.12 through 7.0.0, and 6.4.10 through 6.4.0 allows low privilege attacker to execute arbitrary code with high privilege via spoofed named pipe messages.

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

FortiClientWindows contains an authentication bypass vulnerability where low-privilege attackers can send spoofed named pipe messages to bypass authentication mechanisms and execute arbitrary code with high (system) privileges. The vulnerability exists in the named pipe inter-process communication used by FortiClient for privileged operations.

MitigationUpdate FortiClientWindows to vendor-patched versions (7.4.1, 7.2.5, 7.0.13, 6.4.11 or later) across all affected endpoints to remediate the vulnerability.

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:>= 6.4.0, < 7.0.13>= 7.2.0, < 7.2.5= 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 FortiClientWindows is installed
    Open Programs and Features (appwiz.cpl) or check C:\Program Files\Fortinet\FortiClient\ for the FortiClient application folder
    Affected if FortiClientWindows is present on the endpoint
  2. Determine installed FortiClient version
    Right-click FortiClient icon in system tray, select About, or check the version listed in Programs and Features, or inspect the file version of FortiClient.exe in the installation folder
    Affected if Version cannot be determined or matches the affected ranges below
  3. Compare version against affected ranges
    Check if the installed version falls into: 6.4.0 through 7.0.12; 7.2.0 through 7.2.4; or exactly 7.4.0
    Affected if Installed version is within these ranges: >= 6.4.0 and < 7.0.13, OR >= 7.2.0 and < 7.2.5, OR exactly 7.4.0
  4. Confirm named pipe IPC is in use
    FortiClient uses named pipes for privileged operations by default; verify the FortiClient service is running and the endpoint protection features are enabled
    Affected if FortiClient service is running and the application is active with endpoint protection features enabled

If FortiClientWindows is installed and the version falls within 6.4.0-7.0.12, 7.2.0-7.2.4, or exactly 7.4.0, the environment is affected by this authentication bypass vulnerability.

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.13 / 7.2.5 or later
Fixed in 7.0.137.2.5
Interim mitigation

Update FortiClientWindows to vendor-patched versions (7.4.1, 7.2.5, 7.0.13, 6.4.11 or later) across all affected endpoints to remediate the vulnerability.

Recommended fix High confidence

Upgrade to FortiClient 7.4.1 or later (or 7.2.5+, or 7.0.13+ depending on your major version branch)

  1. 1. Check the current FortiClient Windows version by opening FortiClient and navigating to Help > About, or by running 'fcwin.exe -v' in the command prompt
  2. 2. Based on your current major version, upgrade to the corresponding minimum fixed version: 7.0.13 or later, 7.2.5 or later, or 7.4.1 or later
  3. 3. Download the appropriate FortiClient installer from the official Fortinet support portal (support.fortinet.com) or FortiGuard
  4. 4. Close any running instances of FortiClient before upgrading
  5. 5. Run the installer with administrator privileges and follow the on-screen prompts to complete the upgrade
  6. 6. After installation, verify the version by checking Help > About to confirm the upgrade was successful
  7. 7. Restart the system if prompted to ensure all components are properly updated
Caveat Standard upgrade - review release notes for any configuration or feature changes specific to your version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47574 — 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-47574 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