# CVE-2019-17657: Denial of service in FortiAP-S/W2

> Attackers can cause denial of service on Fortinet admin webUIs by sending slow, crafted HTTP requests, affecting network administrators.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Apr 2020
- **Updated:** 25 Oct 2024
- **Also known as:** ALPINE-CVE-2019-17657, CLEANSTART-2026-LB59576, GHSA-j8g4-vw7x-cwpr

## What is CVE-2019-17657?

CVE-2019-17657 is a high-severity denial of service vulnerability in Fortinet Fortianalyzer, published on 7 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Uncontrolled Resource Consumption vulnerability in Fortinet FortiSwitch below 3.6.11, 6.0.6 and 6.2.2, FortiAnalyzer below 6.2.3, FortiManager below 6.2.3 and FortiAP-S/W2 below 6.2.2 may allow an attacker to cause admin webUI denial of service (DoS) via handling special crafted HTTP requests/responses in pieces slowly, as demonstrated by Slow HTTP DoS Attacks.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2019-17657?

It affects 5 products.


Products: Fortinet Fortianalyzer, Fortinet Fortiap-S, Fortinet Fortiap-W2, Fortinet Fortimanager, Fortinet Fortiswitch.

## How do I fix CVE-2019-17657?

Upgrade to a fixed version.

## Is CVE-2019-17657 being exploited?

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

## Other vulnerabilities in Fortinet Fortianalyzer

- [CVE-2026-24858](https://insights.sbomify.com/CVE-2026-24858/): Fortinet Multiple Products Authentication Bypass Using an Alternate Path or Channel (critical 9.4, exploited in the wild)
- [CVE-2023-25610](https://insights.sbomify.com/CVE-2023-25610/): Memory corruption in FortiAnalyzer (critical 9.3)
- [CVE-2021-32603](https://insights.sbomify.com/CVE-2021-32603/): Server-side request forgery in Fortinet FortiAnalyzer, FortiManager (high 8.8)
- [CVE-2020-12817](https://insights.sbomify.com/CVE-2020-12817/): Cross-site scripting in Fortinet FortiAnalyzer (high 8.8)
- [CVE-2024-48886](https://insights.sbomify.com/CVE-2024-48886/): Auth bypass in FortiOS (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-17657 and fix it if it is affected.

What it is: CVE-2019-17657 is a high-severity denial of service vulnerability in Fortinet Fortianalyzer, published on 7 Apr 2020. 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-2019-17657 in the wild and no public exploit code.

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

## Sources

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

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