# CVE-2018-10968: Hardcoded credentials in n/a

> Attackers can gain unauthorized access to D-Link routers via a default TELNET account, leading to potential device compromise.

- **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:** 18 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m8gx-4w6q-hf55

## What is CVE-2018-10968?

CVE-2018-10968 is a critical vulnerability in n/a, published on 18 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On D-Link DIR-550A and DIR-604M devices through v2.10KR, a malicious user can use a default TELNET account to get unauthorized access to vulnerable devices, aka a backdoor access vulnerability.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

## Which versions are affected by CVE-2018-10968?

It affects 2 products.


Products: D-Link Dir-550a Firmware, D-Link Dir-604m Firmware.

## How do I fix CVE-2018-10968?

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

## Is CVE-2018-10968 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-10967](https://insights.sbomify.com/CVE-2018-10967/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10968 and fix it if it is affected.

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

## Sources

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

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