# CVE-2021-28144: Command injection in n/a

> Remote authenticated attackers can inject arbitrary commands on D-Link DIR-3060 routers via unsafe popen calls, leading to code execution in admin or root contexts.

- **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:** 11 Mar 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-9cvr-344x-r47m

## What is CVE-2021-28144?

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

### Official description

prog.cgi on D-Link DIR-3060 devices before 1.11b04 HF2 allows remote authenticated users to inject arbitrary commands in an admin or root context because SetVirtualServerSettings calls CheckArpTables, which calls popen unsafely.

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

## Which versions are affected by CVE-2021-28144?

It affects 1 product.


Products: Dlink Dir-3060 Firmware.

## How do I fix CVE-2021-28144?

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

## Is CVE-2021-28144 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-44204](https://insights.sbomify.com/CVE-2022-44204/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-28144 and fix it if it is affected.

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

## Sources

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

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