# CVE-2013-4669: Weak cryptography in n/a

> Man-in-the-middle attackers can intercept sensitive data by exploiting FortiClient's failure to halt SSL sessions upon detecting invalid server certificates.

- **Severity:** Medium 5.4 (`AV:N/AC:H/Au:N/C:C/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Jun 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-hrj7-5rgf-5c7r

## What is CVE-2013-4669?

CVE-2013-4669 is a medium-severity vulnerability in Fortinet Forticlient, published on 25 Jun 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

FortiClient 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.

Weakness: CWE-310, CWE-255

## Which versions are affected by CVE-2013-4669?

It affects 3 products.


Products: Fortinet Forticlient, Fortinet Forticlient Lite, Fortinet Forticlient Ssl Vpn.

## How do I fix CVE-2013-4669?

No fix has been published for CVE-2013-4669 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-4669 being exploited?

There is no known exploitation of CVE-2013-4669 in the wild and no public exploit code.

## Other vulnerabilities in Fortinet Forticlient

- [CVE-2019-17658](https://insights.sbomify.com/CVE-2019-17658/): Privilege escalation in Fortinet FortiClientWindows (critical 9.8)
- [CVE-2023-45590](https://insights.sbomify.com/CVE-2023-45590/): Code injection in FortiClientLinux (critical 9.4)
- [CVE-2017-14184](https://insights.sbomify.com/CVE-2017-14184/): Information disclosure in FortiClient SSLVPN Client for Linux (high 8.8)
- [CVE-2016-8493](https://insights.sbomify.com/CVE-2016-8493/): Privilege escalation in Fortinet FortiClient (high 8.8)
- [CVE-2020-15934](https://insights.sbomify.com/CVE-2020-15934/): Privilege escalation in FortiClientLinux (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4669 and fix it if it is affected.

What it is: CVE-2013-4669 is a medium-severity vulnerability in Fortinet Forticlient, published on 25 Jun 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-4669 in the wild and no public exploit code.

Affected product: Fortinet Forticlient. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-4669/ (Markdown: https://insights.sbomify.com/CVE-2013-4669/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-4669
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-4669
- OSV: https://osv.dev/vulnerability/CVE-2013-4669

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-4669/
Summaries are generated and may contain mistakes; the official description above is the record.