# CVE-2019-18852: Hardcoded credentials in n/a

> Attackers can gain unauthorized TELNET access to D-Link routers using hardcoded credentials, leading to full device compromise.

- **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:** 11 Nov 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mpx6-w79q-h86g

## What is CVE-2019-18852?

CVE-2019-18852 is a critical vulnerability in n/a, published on 11 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Certain D-Link devices have a hardcoded Alphanetworks user account with TELNET access because of /etc/config/image_sign or /etc/alpha_config/image_sign. This affects DIR-600 B1 V2.01 for WW, DIR-890L A1 v1.03, DIR-615 J1 v100 (for DCN), DIR-645 A1 v1.03, DIR-815 A1 v1.01, DIR-823 A1 v1.01, and DIR-842 C1 v3.00.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 7 products.


Products: Dlink Dir-600 B1 Firmware, Dlink Dir-615 J1 Firmware, Dlink Dir-645 A1 Firmware, Dlink Dir-815 A1 Firmware, Dlink Dir-823 A1 Firmware, Dlink Dir-842 C1 Firmware, Dlink Dir-890l A1 Firmware.

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

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

## Is CVE-2019-18852 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-12943](https://insights.sbomify.com/CVE-2017-12943/): Path traversal in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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