dbcve.org
ForticlientApplication · Fortinet

CVE-2024-3661

HIGH · 7.6 CVSS v3.1 Published 2024-05-06
Fix available
A fix is available. Upgrade to 1.5.1.25 / 3.7.0.134 or later.
See remediation →
81/100
Remediation priority · High
Public exploit 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
DHCP can add routes to a client’s routing table via the classless static route option (121). VPN-based security solutions that rely on routes to redirect traffic can be forced to leak traffic over the physical interface. An attacker on the same local network can read, disrupt, or possibly modify network traffic that was expected to be protected by the VPN.

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
How this class of weakness works · CWE-306

A sensitive function is reachable with no authentication at all, so anyone who finds the endpoint can use it. These are routinely discovered by automated scanning. The fix is to require and enforce authentication on every privileged path, with no exceptions left open.

General guidance for the missing authentication class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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.2.5= 7.4.0
Anyconnect Vpn ClientApplication
Affected:all versions
Secure ClientApplication
Affected:all versions
GlobalprotectApplication
Affected:all versions
Secure Access ClientApplication
Affected:< 24.06.1< 24.8.5
Big Ip Access Policy ManagerApplication
Affected:>= 7.2.3, <= 7.2.5>= 15.1.0, <= 15.1.10>= 16.1.0, <= 16.1.5>= 17.1.0, <= 17.1.2
Client ConnectorApplication
Affected:< 1.5.1.25< 4.2.0.282>= 3.7, < 3.7.0.134all versions
Ipsec Mobile Vpn ClientApplication
Affected:all versions

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

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

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 1.5.1.25 / 3.7.0.134 / 4.2.0.282 or later
Fixed in 1.5.1.253.7.0.1344.2.0.282
Recommended fix Moderate confidence

Forticlient: 7.2.6+ or 7.4.1+; Secure Access Client: 24.06.1+ or 24.8.5+; Client Connector: 1.5.1.25+/4.2.0.282+/3.7.0.134+; Big IP: contact F5 for specific patch versions

  1. 1. For Forticlient: Upgrade to version 7.2.6 or later, or 7.4.1 or later (addresses versions >= 6.4.0, < 7.2.5 and = 7.4.0)
  2. 2. For Secure Access Client: Upgrade to version 24.06.1 or later, or 24.8.5 or later
  3. 3. For Big IP Access Policy Manager: Apply vendor patches for versions 7.2.3-7.2.5, 15.1.0-15.1.10, 16.1.0-16.1.5, and 17.1.0-17.1.2 (contact F5 Networks for specific patches)
  4. 4. For Client Connector: Upgrade to 1.5.1.25 or later, 4.2.0.282 or later, or 3.7.0.134 or later as applicable
  5. 5. For other affected products (Anyconnect, Secure Client, Globalprotect, Ipsec Mobile Vpn): Contact respective vendors (Cisco, Palo Alto Networks, etc.) for patches or configuration guidance
  6. 6. Consider network-level mitigations: isolate VPN clients on separate VLANs, configure DHCP servers to block option 121, or implement network access control
Caveat Upgrade may require client reinstall or configuration changes; test VPN connectivity and routing policies in staging before production deployment

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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