# CVE-2015-1571: Weak cryptography in n/a

> Man-in-the-middle attackers could potentially spoof SSL servers due to shared certificates in FortiOS CAPWAP DTLS, though vendor disputes exploitability.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-j86q-w3f9-5q6c

## What is CVE-2015-1571?

CVE-2015-1571 is a medium-severity vulnerability in Fortinet Fortios, published on 10 Feb 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The CAPWAP DTLS protocol implementation in Fortinet FortiOS 5.0 Patch 7 build 4457 uses the same certificate and private key across different customers' installations, which makes it easier for man-in-the-middle attackers to spoof SSL servers by leveraging the Fortinet_Factory certificate and private key.  NOTE: FG-IR-15-002 says "The Fortinet_Factory certificate is unique to each device ... An attacker cannot therefore stage a MitM attack.

Weakness: CWE-310

## Which versions are affected by CVE-2015-1571?

It affects 1 product.


Products: Fortinet Fortios.

## How do I fix CVE-2015-1571?

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

## Is CVE-2015-1571 being exploited?

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

## Other vulnerabilities in Fortinet Fortios

- [CVE-2024-23113](https://insights.sbomify.com/CVE-2024-23113/): Fortinet Multiple Products Format String (critical 9.8, exploited in the wild)
- [CVE-2022-40684](https://insights.sbomify.com/CVE-2022-40684/): Fortinet Multiple Products Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2024-55591](https://insights.sbomify.com/CVE-2024-55591/): Fortinet FortiOS and FortiProxy Authentication Bypass (critical 9.6, exploited in the wild)
- [CVE-2024-21762](https://insights.sbomify.com/CVE-2024-21762/): Fortinet FortiOS Out-of-Bound Write (critical 9.6, exploited in the wild)
- [CVE-2022-42475](https://insights.sbomify.com/CVE-2022-42475/): Fortinet FortiOS Heap-Based Buffer Overflow (critical 9.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1571 and fix it if it is affected.

What it is: CVE-2015-1571 is a medium-severity vulnerability in Fortinet Fortios, published on 10 Feb 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-1571 in the wild and no public exploit code.

Affected product: Fortinet Fortios. 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-2015-1571/ (Markdown: https://insights.sbomify.com/CVE-2015-1571/index.md)
```

## Sources

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

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