# CVE-2020-6842: Command injection in n/a

> Remote authenticated administrators can execute arbitrary OS commands on D-Link media renderers via shell metacharacters in the device name.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-ch6v-3x5q-gm5j

## What is CVE-2020-6842?

CVE-2020-6842 is a high-severity command injection vulnerability in n/a, published on 21 Feb 2020. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

D-Link DCH-M225 1.05b01 and earlier devices allow remote authenticated admins to execute arbitrary OS commands via shell metacharacters in the media renderer name.

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

## Which versions are affected by CVE-2020-6842?

It affects 1 product.


Products: Dlink Dch-M225 Firmware.

## How do I fix CVE-2020-6842?

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

## Is CVE-2020-6842 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-6841](https://insights.sbomify.com/CVE-2020-6841/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-6842 and fix it if it is affected.

What it is: CVE-2020-6842 is a high-severity command injection vulnerability in n/a, published on 21 Feb 2020. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-6842 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-2020-6842/ (Markdown: https://insights.sbomify.com/CVE-2020-6842/index.md)
```

## Sources

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

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