dbcve.org
ForticlientApplication · Fortinet

CVE-2024-54019

MEDIUM · 6.5 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 7.2.7 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges 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 improper validation of certificate with host mismatch in Fortinet FortiClientWindows version 7.4.0, versions 7.2.0 through 7.2.6, and 7.0 all versions allow an unauthorized attacker to redirect VPN connections via DNS spoofing or another form of redirection.

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 fails to properly validate that SSL/TLS certificates match the intended VPN host, allowing an attacker on the same network to perform DNS spoofing and redirect VPN connections to a malicious server. This enables man-in-the-middle attacks on VPN traffic.

MitigationUpgrade FortiClientWindows to the latest patched version as released by Fortinet. Until then, ensure VPN connections occur only on trusted networks and consider implementing additional network-level controls to detect DNS spoofing.

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.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Identify FortiClientWindows version
    Open FortiClient, click the hamburger menu (top left), select About, or run 'reg query "HKLM\SOFTWARE\Fortinet\FortiClient" /v Version' in Command Prompt
    Affected if The displayed version matches the affected ranges: 7.0.0 through 7.2.6, or exactly 7.4.0
  2. Confirm VPN functionality is in use
    Verify that FortiClient is configured with any VPN profiles (SSLVPN or IPsec VPN)
    Affected if VPN profiles are configured and active on the endpoint
  3. Check for certificate validation settings (optional)
    In FortiClient, navigate to VPN settings and examine the connection configuration for any custom SSL/TLS settings
    Affected if Custom SSL settings that might disable certificate validation are enabled (though the flaw exists regardless in vulnerable versions)

If the installed FortiClientWindows version is 7.0.0 through 7.2.6, or exactly 7.4.0, and the software is used for VPN connections, the environment is affected by this certificate validation 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.2.7 or later
Fixed in 7.2.7
Interim mitigation

Upgrade FortiClientWindows to the latest patched version as released by Fortinet. Until then, ensure VPN connections occur only on trusted networks and consider implementing additional network-level controls to detect DNS spoofing.

Recommended fix High confidence

FortiClient 7.2.7 or later (for 7.0.x/7.2.x users); FortiClient 7.4.1 or later (for 7.4.0 users)

  1. 1. Identify the currently installed FortiClient version from Help > About FortiClient
  2. 2. For FortiClient 7.0.x users: Download and install FortiClient 7.2.7 or later from https://www.fortinet.com/support/product-downloads#clients
  3. 3. For FortiClient 7.2.0-7.2.6 users: Download and install FortiClient 7.2.7 or later from the Fortinet support portal
  4. 4. For FortiClient 7.4.0 users: Download and install FortiClient 7.4.1 or later from the Fortinet support portal
  5. 5. After installation, verify the version via Help > About FortiClient to confirm the update was successful
Caveat Standard upgrade considerations apply - ensure compatibility with your VPN infrastructure and test in a non-production environment first

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

Fix this in Forticlient Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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