ForticlientApplication · Fortinet
CVE-2013-4669
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 · uneditedFortiClient before 4.3.5.472 on Windows, before 4.0.3.134 on Mac OS X, and before 4.0 on Android; FortiClient Lite before 4.3.4.461 on Windows; FortiClient Lite 2.0 through 2.0.0223 on Android; and FortiClient SSL VPN before 4.0.2258 on Linux proceed with an SSL session after determining that the server's X.509 certificate is invalid, which allows man-in-the-middle attackers to obtain sensitive information by leveraging a password transmission that occurs before the user warning about the certificate problem.
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 confidenceFortiClient contains an SSL certificate validation bypass vulnerability where the software proceeds with an SSL session after determining that the server's X.509 certificate is invalid. Passwords are transmitted before the user is warned about the certificate problem, allowing man-in-the-middle attackers to intercept sensitive credentials.
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
<= 4.3.3.445<= 4.0.2
Forticlient LiteApplication
<= 4.3.3.445<= 2.0
Forticlient Ssl VpnApplication
<= 4.0.2012CVSS 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
- High
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- None
- Availability
- None
AV:N/AC:H/Au:N/C:C/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed FortiClient productCheck the installed software for FortiClient, FortiClient Lite, or FortiClient SSL VPN. This may be listed in Add/Remove Programs, the application itself, or the software inventory.Affected if Any of these three products is installed, proceed to version check.
-
Determine the installed versionLocate the version number of the FortiClient installation. This is typically visible in the application UI under Help > About, or in the Windows Programs and Features list.Affected if Version is revealed, proceed to comparison.
-
Compare version against affected rangesMatch your installed version against: FortiClient <= 4.3.3.445 or <= 4.0.2; FortiClient Lite <= 4.3.3.445 or <= 2.0; FortiClient SSL VPN <= 4.0.2012.Affected if Your version falls within any of these ranges, you are potentially affected.
-
Confirm SSL VPN feature is in useDetermine whether the FortiClient installation is configured to use SSL VPN connectivity to remote networks. This vulnerability specifically affects SSL VPN sessions.Affected if SSL VPN connections are configured or frequently used, the exploitation condition is met.
You are affected if you have FortiClient, FortiClient Lite, or FortiClient SSL VPN installed with a version within the affected ranges and you use SSL VPN functionality.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade FortiClient to version 4.3.5.472 or later on Windows, 4.0.3.134 or later on Mac OS X, and 4.0 or later on Android. For FortiClient Lite, upgrade to 4.3.4.461 or later on Windows. FortiClient SSL VPN on Linux should be updated to 4.0.2258 or later.
Fix this in Forticlient
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2013-4669 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-4669 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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