# CVE-2019-20215: Command injection in n/a

> Remote attackers can execute arbitrary OS commands on D-Link DIR-859 routers via a crafted M-SEARCH request due to improper input handling.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jan 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xj55-9jj5-7q99

## What is CVE-2019-20215?

CVE-2019-20215 is a critical command injection vulnerability in n/a, published on 29 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

D-Link DIR-859 1.05 and 1.06B01 Beta01 devices allow remote attackers to execute arbitrary OS commands via a urn: to the M-SEARCH method in ssdpcgi() in /htdocs/cgibin, because HTTP_ST is mishandled. The value of the urn: service/device is checked with the strstr function, which allows an attacker to concatenate arbitrary commands separated by shell metacharacters.

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

## Which versions are affected by CVE-2019-20215?

It affects 1 product.


Products: Dlink Dir-859 Firmware.

## How do I fix CVE-2019-20215?

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

## Is CVE-2019-20215 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-20215 exists.

Public exploit code:

- D-Link Unauthenticated Remote Command Execution using UPnP via a special crafted M-SEARCH packet. (metasploit)
- D-Link Devices Unauthenticated Remote Command Execution in ssdpcgi (metasploit)
- D-Link Devices - Unauthenticated Remote Command Execution in ssdpcgi (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2024-0769](https://insights.sbomify.com/CVE-2024-0769/): D-Link DIR-859 Router Path Traversal (medium 5.3, exploited in the wild)
- [CVE-2019-20216](https://insights.sbomify.com/CVE-2019-20216/): Command injection in n/a (critical 9.8)
- [CVE-2019-20217](https://insights.sbomify.com/CVE-2019-20217/): Command injection in n/a (critical 9.8)
- [CVE-2023-36092](https://insights.sbomify.com/CVE-2023-36092/): Auth bypass in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-20215 and fix it if it is affected.

What it is: CVE-2019-20215 is a critical command injection vulnerability in n/a, published on 29 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-20215 exists.

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-2019-20215/ (Markdown: https://insights.sbomify.com/CVE-2019-20215/index.md)
```

## Sources

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

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