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

> Attackers can gain administrative access to D-Link cameras using a hardcoded password stored in a read-only filesystem.

- **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:** 2 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3qrh-88fr-gvx6

## What is CVE-2017-8415?

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

### Official description

An issue was discovered on D-Link DCS-1100 and DCS-1130 devices. The device has a custom telnet daemon as a part of the busybox and retrieves the password from the shadow file using the function getspnam at address 0x00053894. Then performs a crypt operation on the password retrieved from the user at address 0x000538E0 and performs a strcmp at address 0x00053908 to check if the password is correct or incorrect. However, the /etc/shadow file is a part of CRAM-FS filesystem which means that the user cannot change the password and hence a hardcoded hash in /etc/shadow is used to match the credentials provided by the user. This is a salted hash of the string "admin" and hence it acts as a password to the device which cannot be changed as the whole filesystem is read only.

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

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

It affects 2 products.


Products: Dlink Dcs-1100 Firmware, Dlink Dcs-1130 Firmware.

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

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

## Is CVE-2017-8415 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-1599](https://insights.sbomify.com/CVE-2013-1599/): Command injection in n/a (critical 9.8)
- [CVE-2017-8410](https://insights.sbomify.com/CVE-2017-8410/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-8412](https://insights.sbomify.com/CVE-2017-8412/): Memory corruption in n/a (high 8.8)
- [CVE-2017-8413](https://insights.sbomify.com/CVE-2017-8413/): Command injection in n/a (high 8.8)
- [CVE-2017-8416](https://insights.sbomify.com/CVE-2017-8416/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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