# CVE-2017-8410: Memory corruption in n/a

> A stack-based buffer overflow in the RTSP handler allows remote attackers to execute arbitrary code on D-Link IP cameras.

- **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-6j69-2rj4-cxq6

## What is CVE-2017-8410?

CVE-2017-8410 is a critical memory corruption 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 binary rtspd in /sbin folder of the device handles all the rtsp connections received by the device. It seems that the binary performs a memcpy operation at address 0x00011E34 with the value sent in the "Authorization: Basic" RTSP header and stores it on the stack. The number of bytes to be copied are calculated based on the length of the string sent in the RTSP header by the client. As a result, memcpy copies more data then it can hold on stack and this results in corrupting the registers for the caller function sub_F6CC which results in memory corruption. The severity of this attack is enlarged by the fact that the same value is then copied on the stack in the function 0x00011378 and this allows to overflow the buffer allocated and thus control the PC register which will result in arbitrary code execution on the device.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 2 products.


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

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

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

## Is CVE-2017-8410 being exploited?

There is no known exploitation of CVE-2017-8410 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-8415](https://insights.sbomify.com/CVE-2017-8415/): Hardcoded credentials 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-8410 and fix it if it is affected.

What it is: CVE-2017-8410 is a critical memory corruption 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-8410 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-8410/ (Markdown: https://insights.sbomify.com/CVE-2017-8410/index.md)
```

## Sources

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

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