# CVE-2017-1000020: Auth bypass in n/a

> Attackers can bypass authentication on eCos-based embedded devices by sending SYN or FIN flood packets, leading to remote device takeover.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 13 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** CVE-2017-5861, GHSA-76v3-hrq5-hh93

## What is CVE-2017-1000020?

CVE-2017-1000020 is a critical authentication bypass vulnerability in n/a, published on 13 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SYN Flood or FIN Flood attack in ECos 1 and other versions embedded devices results in web Authentication Bypass. "eCos Embedded Web Servers used by Multiple Routers and Home devices, while sending SYN Flood or FIN Flood packets fails to validate and handle the packets and does not ask for any sign of authentication resulting in Authentication Bypass. An attacker can take complete advantage of this bug and take over the device remotely or locally. The bug has been successfully tested and reproduced in some versions of SOHO Routers manufactured by TOTOLINK, GREATEK and others."

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2017-1000020?

It affects 1 product.


Products: Ecos Embedded Web Servers.

## How do I fix CVE-2017-1000020?

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

## Is CVE-2017-1000020 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1000020 and fix it if it is affected.

What it is: CVE-2017-1000020 is a critical authentication bypass vulnerability in n/a, published on 13 Jul 2017. 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-2017-1000020 in the wild and no public exploit code.

Affected product: n/a. 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-2017-1000020/ (Markdown: https://insights.sbomify.com/CVE-2017-1000020/index.md)
```

## Sources

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

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