CVE-2017-8413

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.

• CWE-77

• http://packetstormsecurity.com/files/153226/Dlink-DCS-1130-Command-Injection-CSRF-Stack-Overflow.htmlThird Party Advisory, VDB Entry
• https://github.com/ethanhunnt/IoT_vulnerabilities/blob/master/Dlink_DCS_1130_security.pdfNot Applicable, Third Party Advisory
• https://seclists.org/bugtraq/2019/Jun/8Mailing List, Third Party Advisory
• http://packetstormsecurity.com/files/153226/Dlink-DCS-1130-Command-Injection-CSRF-Stack-Overflow.htmlThird Party Advisory, VDB Entry
• https://github.com/ethanhunnt/IoT_vulnerabilities/blob/master/Dlink_DCS_1130_security.pdfNot Applicable, Third Party Advisory
• https://seclists.org/bugtraq/2019/Jun/8Mailing List, Third Party Advisory

Published

Jul 2, 2019

Last Modified

Jun 17, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2017-8407An issue was discovered on D-Link DCS-1130 devices. The devi…8.8
• CVE-2017-8408An issue was discovered on D-Link DCS-1130 devices. The devi…
• CVE-2017-8409An issue was discovered on D-Link DCS-1130 devices. The devi…7.5
• CVE-2017-8410An issue was discovered on D-Link DCS-1100 and DCS-1130 devi…9.8
• CVE-2017-8411An issue was discovered on D-Link DCS-1130 devices. The devi…8.8
• CVE-2017-8412An issue was discovered on D-Link DCS-1100 and DCS-1130 devi…8.8
• CVE-2017-8414An issue was discovered on D-Link DCS-1100 and DCS-1130 devi…7.8
• CVE-2017-8415An issue was discovered on D-Link DCS-1100 and DCS-1130 devi…9.8
• CVE-2017-8416An issue was discovered on D-Link DCS-1100 and DCS-1130 devi…8.8
• CVE-2017-8417An issue was discovered on D-Link DCS-1100 and DCS-1130 devi…8.8
• CVE-2017-8418RuboCop 0.48.1 and earlier does not use /tmp in safe way, al…
• CVE-2017-8419LAME through 3.99.5 relies on the signed integer data type f…