# CVE-2017-11436: Hardcoded credentials in n/a

> A hardcoded backdoor admin account allows remote attackers to gain unauthorized access and potentially execute code via Telnet on D-Link DIR-615 routers.

- **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:** 19 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pfhr-qvv5-jqp2

## What is CVE-2017-11436?

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

### Official description

D-Link DIR-615 before v20.12PTb04 has a second admin account with a 0x1 BACKDOOR value, which might allow remote attackers to obtain access via a TELNET connection.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Dlink Dir-615.

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

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

## Is CVE-2017-11436 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-7405](https://insights.sbomify.com/CVE-2017-7405/): Auth bypass in n/a (critical 9.8)
- [CVE-2017-7406](https://insights.sbomify.com/CVE-2017-7406/): Weak cryptography in n/a (critical 9.8)
- [CVE-2017-7404](https://insights.sbomify.com/CVE-2017-7404/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2009-4821](https://insights.sbomify.com/CVE-2009-4821/): Auth bypass in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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