# CVE-2017-8413: Command injection in n/a > Unauthenticated attackers can execute arbitrary commands on D-Link cameras via a UDP packet containing a base64-encoded command string. - **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-q4mq-mjm9-5j2x ## What is CVE-2017-8413? CVE-2017-8413 is a high-severity command injection 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 runs a custom daemon on UDP port 5978 which is called "dldps2121" and listens for broadcast packets sent on 255.255.255.255. This daemon handles custom D-Link UDP based protocol that allows D-Link mobile applications and desktop applications to discover D-Link devices on the local network. The binary processes the received UDP packets sent from any device in "main" function. One path in the function traverses towards a block of code that handles commands to be executed on the device. The custom protocol created by D-Link follows the following pattern: Packetlen, Type of packet; M=MAC address of device or broadcast; D=Device Type;C=base64 encoded command string;test=1111. If a packet is received with the packet type being "S" or 0x53 then the string passed in the "C" parameter is base64 decoded and then executed by passing into a System API. We can see at address 0x00009B44 that the string received in packet type subtracts 0x31 or "1" from the packet type and is compared against 0x22 or "double quotes". If that is the case, then the packet is sent towards the block of code that executes a command. Then the value stored in "C" parameter is extracted at address 0x0000A1B0. Finally, the string received is base 64 decoded and passed on to the system API at address 0x0000A2A8 as shown below. The same form of communication can be initiated by any process including an attacker process on the mobile phone or the desktop and this allows a third-party application on the device to execute commands on the device without any authentication by sending just 1 UDP packet with custom base64 encoding. Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command) ## Which versions are affected by CVE-2017-8413? It affects 2 products. Products: Dlink Dcs-1100 Firmware, Dlink Dcs-1130 Firmware. ## How do I fix CVE-2017-8413? No fix has been published for CVE-2017-8413 yet. Limit exposure of the affected software until one is available. ## Is CVE-2017-8413 being exploited? There is no known exploitation of CVE-2017-8413 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-8412](https://insights.sbomify.com/CVE-2017-8412/): Memory corruption 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-8413 and fix it if it is affected. What it is: CVE-2017-8413 is a high-severity command injection 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-8413 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-8413/ (Markdown: https://insights.sbomify.com/CVE-2017-8413/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-8413 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-8413 - OSV: https://osv.dev/vulnerability/CVE-2017-8413 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-8413/ Summaries are generated and may contain mistakes; the official description above is the record.