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

> Remote attackers with admin access can execute arbitrary commands on SMC Networks routers via parameter pollution in the diagnostic tools.

- **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:** 27 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2rhc-f5j3-jr26

## What is CVE-2020-8087?

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

### Official description

SMC Networks D3G0804W D3GNV5M-3.5.1.6.10_GA devices allow remote command execution by leveraging access to the Network Diagnostic Tools screen, as demonstrated by an admin login. The attacker must use a Parameter Pollution approach against goform/formSetDiagnosticToolsFmPing by providing the vlu_diagnostic_tools__ping_address parameter twice: once with a shell metacharacter and a command name, and once with a command argument.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Smc D3g0804w Firmware.

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

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

## Is CVE-2020-8087 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8087 is a critical command injection vulnerability in n/a, published on 27 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-8087 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-8087/ (Markdown: https://insights.sbomify.com/CVE-2020-8087/index.md)
```

## Sources

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

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