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

> A stack-based buffer overflow in the mp4ts binary allows remote attackers to execute arbitrary code via crafted HTTP requests.

- **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:** 2 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c5p6-2wgp-hcc2

## What is CVE-2017-8412?

CVE-2017-8412 is a high-severity memory corruption vulnerability in n/a, published on 2 Jul 2019. It can only be exploited from the same machine or local network, 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 binary called mp4ts under the /var/www/video folder. It seems that this binary dumps the HTTP VERB in the system logs. As a part of doing that it retrieves the HTTP VERB sent by the user and uses a vulnerable sprintf function at address 0x0000C3D4 in the function sub_C210 to copy the value into a string and then into a log file. Since there is no bounds check being performed on the environment variable at address 0x0000C360 this results in a stack overflow and overwrites the PC register allowing an attacker to execute buffer overflow or even a command injection attack.

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

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

It affects 2 products.


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

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

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

## Is CVE-2017-8412 being exploited?

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

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

## Sources

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

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