# CVE-2019-6015: Denial of service in FON2601E-SE, FON2601E-RE, FON2601E-FSW-S, and FON2601E-FSW-B

> FON routers act as open resolvers, allowing attackers to use them for DNS amplification attacks against third parties.

- **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:** No
- **Published:** 4 Oct 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-88x6-gq74-9xxv

## What is CVE-2019-6015?

CVE-2019-6015 is a high-severity denial of service vulnerability in FON2601E-SE, FON2601E-RE, FON2601E-FSW-S, and FON2601E-FSW-B, published on 4 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FON2601E-SE, FON2601E-RE, FON2601E-FSW-S, and FON2601E-FSW-B with firmware versions 1.1.7 and earlier contain an issue where they may behave as open resolvers. If this vulnerability is exploited, FON routers may be leveraged for DNS amplification attacks to some other entities.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 4 products.


Products: Fon Fon2601e-Fsw-B Firmware, Fon Fon2601e-Fsw-S Firmware, Fon Fon2601e-Re Firmware, Fon Fon2601e-Se Firmware.

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

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

## Is CVE-2019-6015 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6015 is a high-severity denial of service vulnerability in FON2601E-SE, FON2601E-RE, FON2601E-FSW-S, and FON2601E-FSW-B, published on 4 Oct 2019. 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-6015 in the wild and no public exploit code.

Affected product: FON2601E-SE, FON2601E-RE, FON2601E-FSW-S, and FON2601E-FSW-B. 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-6015/ (Markdown: https://insights.sbomify.com/CVE-2019-6015/index.md)
```

## Sources

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

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