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

> An admin can execute arbitrary OS commands via shell metacharacters in the CLI, affecting D-Link DSL-GS225 devices.

- **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:** 10 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2ccr-95gx-57p2

## What is CVE-2020-6765?

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

### Official description

D-Link DSL-GS225 J1 AU_1.0.4 devices allow an admin to execute OS commands by placing shell metacharacters after a supported CLI command, as demonstrated by ping -c1 127.0.0.1; cat/etc/passwd. The CLI is reachable by TELNET.

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

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

It affects 1 product.


Products: Dlink Dsl-Gs225 Firmware.

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

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

## Is CVE-2020-6765 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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