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

> Authenticated attackers can execute arbitrary commands on Comtrend VR-3033 routers via shell metacharacters in diagnostic pages.

- **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:** 5 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9695-x59r-82q9

## What is CVE-2020-10173?

CVE-2020-10173 is a high-severity command injection vulnerability in n/a, published on 5 Mar 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Comtrend VR-3033 DE11-416SSG-C01_R02.A2pvI042j1.d26m devices have Multiple Authenticated Command Injection vulnerabilities via the ping and traceroute diagnostic pages, as demonstrated by shell metacharacters in the pingIpAddress parameter to ping.cgi.

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

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

It affects 1 product.


Products: Comtrend Vr-3033 Firmware.

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

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

## Is CVE-2020-10173 being exploited?

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

Public exploit code:

- Comtrend VR-3033 - Command Injection (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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