# CVE-2022-42156: Command injection in n/a

> Attackers can execute arbitrary commands on D-Link COVR routers via the tomography_ping_number parameter in SetNetworkTomographySettings.

- **Severity:** High 8.8 (`CVSS:3.1/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:** 13 Oct 2022
- **Updated:** 15 May 2025
- **Also known as:** GHSA-7rf6-xmxm-mxrr

## What is CVE-2022-42156?

CVE-2022-42156 is a high-severity command injection vulnerability in n/a, published on 13 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

D-Link COVR 1200,1203 v1.08 was discovered to contain a command injection vulnerability via the tomography_ping_number parameter at function SetNetworkTomographySettings.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2022-42156?

It affects 3 products.


Products: Dlink Covr 1200 Firmware, Dlink Covr 1202 Firmware, Dlink Covr 1203 Firmware.

## How do I fix CVE-2022-42156?

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

## Is CVE-2022-42156 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-42160](https://insights.sbomify.com/CVE-2022-42160/): Command injection in n/a (high 8.8)
- [CVE-2022-42161](https://insights.sbomify.com/CVE-2022-42161/): Command injection in n/a (high 8.8)
- [CVE-2022-42159](https://insights.sbomify.com/CVE-2022-42159/): Weak cryptography in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-42156 and fix it if it is affected.

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

## Sources

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

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