CVE-2016-20017
RCE in Dlink Dsl-2750B Firmware ≤ 1.05
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2016-20017 is a critical-severity Command Injection (CWE-77) vulnerability in Dlink Dsl-2750B Firmware. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 0.8% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
D-Link DSL-2750B devices running firmware versions prior to 1.05 contain a command injection vulnerability in the login.cgi endpoint. The flaw, tracked as CVE-2016-20017 and assigned CWE-77, permits unauthenticated remote attackers to supply arbitrary commands through the cli parameter, resulting in a CVSS 3.1 score of 9.8.
An attacker with network access to the WAN or LAN interface can submit a crafted HTTP request to login.cgi and execute operating-system commands without credentials. Successful exploitation grants full control over the device, including the ability to read or modify configuration data, install persistent malware, or use the router as an entry point into attached networks.
D-Link published security announcement SAP10088 and made firmware version 1.05 available to address the issue. Public references also include exploit code on Exploit-DB and multiple Full Disclosure postings that document the injection vector.
The vulnerability was actively exploited in the wild between 2016 and 2022.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2016-3105
Vulnerability Data
D-Link DSL-2750B devices before 1.05 allow remote unauthenticated command injection via the login.cgi cli parameter, as exploited in the wild in 2016 through 2022.
- CWE(s)
- KEV Date Added
- 08 January 2024
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.3V1.2.5V1.2.8V1.2.9
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and neutralization that prevent command injection.
Runtime monitoring of software and data can detect anomalous command execution resulting from injection.
Identifying recorded vulnerabilities enables remediation of command-injection flaws before exploitation.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.
Security testing in development catches command-injection vulnerabilities before release.
Secure development life cycle mandates input validation and command construction practices that directly prevent command injection.
Application security requirements explicitly call for controls against injection flaws including command injection.
Secure architecture principles reduce the attack surface but do not prescribe the specific neutralization techniques needed.
Environment separation limits the blast radius of an exploited command injection but does not prevent the flaw itself.