# CVE-2024-41616: Hardcoded credentials in n/a

> Hardcoded credentials in the Telnet service allow attackers to gain unauthorized access and potentially execute code on the device.

- **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:** 6 Aug 2024
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hp2w-73jh-3x82

## What is CVE-2024-41616?

CVE-2024-41616 is a high-severity vulnerability in n/a, published on 6 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

D-Link DIR-300 REVA FIRMWARE v1.06B05_WW contains hardcoded credentials in the Telnet service.

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

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

It affects 1 product.


Products: Dlink Dir-300 Firmware.

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

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

## Is CVE-2024-41616 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-4723](https://insights.sbomify.com/CVE-2011-4723/): D-Link DIR-300 Router Cleartext Storage of a Password (medium 5.7, exploited in the wild)
- [CVE-2013-10069](https://insights.sbomify.com/CVE-2013-10069/): D-Link Devices Unauthenticated RCE (critical 10.0)
- [CVE-2023-31814](https://insights.sbomify.com/CVE-2023-31814/): Path traversal in n/a (critical 9.8)
- [CVE-2013-7471](https://insights.sbomify.com/CVE-2013-7471/): Command injection in n/a (critical 9.8)
- [CVE-2013-10048](https://insights.sbomify.com/CVE-2013-10048/): D-Link Devices command.php Unauthenticated RCE (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-41616 is a high-severity vulnerability in n/a, published on 6 Aug 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-41616 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-2024-41616/ (Markdown: https://insights.sbomify.com/CVE-2024-41616/index.md)
```

## Sources

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

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