# CVE-2017-8411: Command injection in n/a

> Attackers can execute arbitrary commands on D-Link DCS-1130 cameras via the email configuration interface, potentially compromising the device.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-36w9-jg9q-m4qx

## What is CVE-2017-8411?

CVE-2017-8411 is a high-severity command injection vulnerability in n/a, published on 2 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue was discovered on D-Link DCS-1130 devices. The device provides a user with the capability of setting a SMB folder for the video clippings recorded by the device. It seems that the POST parameters passed in this request (to test if email credentials and hostname sent to the device work properly) result in being passed as commands to a "system" API in the function and thus result in command injection on the device. If the firmware version is dissected using binwalk tool, we obtain a cramfs-root archive which contains the filesystem set up on the device that contains all the binaries. The library "libmailutils.so" is the one that has the vulnerable function "sub_1FC4" that receives the values sent by the POST request. If we open this binary in IDA-pro we will notice that this follows an ARM little endian format. The function sub_1FC4 in IDA pro is identified to be receiving the values sent in the POST request and the value set in POST parameter "receiver1" is extracted in function "sub_15AC" which is then passed to the vulnerable system API call. The vulnerable library function is accessed in "cgibox" binary at address 0x00023BCC which calls the "Send_mail" function in "libmailutils.so" binary as shown below which results in the vulnerable POST parameter being passed to the library which results in the command injection issue.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 1 product.


Products: Dlink Dcs-1130 Firmware.

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

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

## Is CVE-2017-8411 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-8404](https://insights.sbomify.com/CVE-2017-8404/): Command injection in n/a (critical 9.8)
- [CVE-2017-8408](https://insights.sbomify.com/CVE-2017-8408/): Command injection in n/a (critical 9.8)
- [CVE-2017-8406](https://insights.sbomify.com/CVE-2017-8406/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2017-8407](https://insights.sbomify.com/CVE-2017-8407/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2017-8409](https://insights.sbomify.com/CVE-2017-8409/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8411 is a high-severity command injection vulnerability in n/a, published on 2 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-8411 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-8411/ (Markdown: https://insights.sbomify.com/CVE-2017-8411/index.md)
```

## Sources

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

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