# CVE-2021-39613: Hardcoded credentials in n/a

> Hard-coded credentials in D-Link VoIP gateways allow attackers to gain unauthorized access and escalate privileges.

- **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:** 23 Aug 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j243-jvh7-7j64

## What is CVE-2021-39613?

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

### Official description

D-Link DVG-3104MS version 1.0.2.0.3, 1.0.2.0.4, and 1.0.2.0.4E contains hard-coded credentials for undocumented user accounts in the '/etc/passwd' file. As weak passwords have been used, the plaintext passwords can be recovered from the hash values. NOTE: This vulnerability only affects products that are no longer supported by the maintainer

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

## Which versions are affected by CVE-2021-39613?

It affects 1 product.


Products: Dlink Dvg-3104ms Firmware.

## How do I fix CVE-2021-39613?

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

## Is CVE-2021-39613 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-39613 and fix it if it is affected.

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

## Sources

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

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