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

> Remote authenticated attackers can execute arbitrary code on D-Link IP cameras via command injection in the web server's AdminID field.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-55r4-xf6q-8cq9

## What is CVE-2017-17020?

CVE-2017-17020 is a high-severity command injection vulnerability in n/a, published on 1 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

On D-Link DCS-5009 devices with firmware 1.08.11 and earlier, DCS-5010 devices with firmware 1.14.09 and earlier, and DCS-5020L devices with firmware before 1.15.01, command injection in alphapd (binary responsible for running the camera's web server) allows remote authenticated attackers to execute code through sanitized /setSystemAdmin user input in the AdminID field being passed directly to a call to system.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 3 products.


Products: Dlink Dcs-5009 Firmware, Dlink Dcs-5010 Firmware, Dlink Dcs-5020l Firmware.

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

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

## Is CVE-2017-17020 being exploited?

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

Public exploit code:

- DLINK DCS-5020L - Remote Code Execution (PoC) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17020 is a high-severity command injection vulnerability in n/a, published on 1 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-17020 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-17020/ (Markdown: https://insights.sbomify.com/CVE-2017-17020/index.md)
```

## Sources

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

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