# CVE-2019-18666: Auth bypass in n/a

> Remote attackers can bypass authentication to enable telnet and gain root access on D-Link DAP-1360 devices via an undocumented HTTP request.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 15 May 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-56wp-9gq8-gjg2

## What is CVE-2019-18666?

CVE-2019-18666 is a critical authentication bypass vulnerability in n/a, published on 15 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on D-Link DAP-1360 revision F devices. Remote attackers can start a telnet service without authorization via an undocumented HTTP request. Although this is the primary vulnerability, the impact depends on the firmware version. Versions 609EU through 613EUbeta were tested. Versions through 6.12b01 have weak root credentials, allowing an attacker to gain remote root access. After 6.12b01, the root credentials were changed but the telnet service can still be started without authorization.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Dlink Dap-1360 Revision F Firmware.

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

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

## Is CVE-2019-18666 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-18666 is a critical authentication bypass vulnerability in n/a, published on 15 May 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-18666 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-2019-18666/ (Markdown: https://insights.sbomify.com/CVE-2019-18666/index.md)
```

## Sources

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

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