# CVE-2024-6045: D-Link router - Hidden Backdoor

> Unauthenticated attackers on the local network can enable Telnet and log in using hardcoded credentials to gain full control of the router.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-m8cg-23fc-95h8

## What is CVE-2024-6045?

CVE-2024-6045 is a high-severity vulnerability in D-Link E15, published on 17 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Certain models of D-Link wireless routers contain an undisclosed factory testing backdoor. Unauthenticated attackers on the local area network can force the device to enable Telnet service by accessing a specific URL and can log in by using the administrator credentials obtained from analyzing the firmware.

Weakness: CWE-912 (Hidden Functionality), CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2024-6045?


## How do I fix CVE-2024-6045?

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

## Is CVE-2024-6045 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6045 and fix it if it is affected.

What it is: CVE-2024-6045 is a high-severity vulnerability in D-Link E15, published on 17 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-6045 in the wild and no public exploit code.

Affected product: D-Link E15. 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-2024-6045/ (Markdown: https://insights.sbomify.com/CVE-2024-6045/index.md)
```

## Sources

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

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