# CVE-2019-16213: Command injection in n/a

> Remote authenticated attackers can execute arbitrary commands with root privileges on Tenda PA6 devices via crafted device name inputs.

- **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:** 25 Jun 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-74vv-phcc-fqx3

## What is CVE-2019-16213?

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

### Official description

Tenda PA6 Wi-Fi Powerline extender 1.0.1.21 could allow a remote authenticated attacker to execute arbitrary commands on the system. By sending a specially crafted string, an attacker could modify the device name of an attached PLC adapter to inject and execute arbitrary commands on the system with root privileges.

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

## Which versions are affected by CVE-2019-16213?

It affects 1 product.


Products: Tendacn Pa6 Firmware.

## How do I fix CVE-2019-16213?

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

## Is CVE-2019-16213 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-0535](https://insights.sbomify.com/CVE-2024-0535/): Tenda PA6 httpd portmap cgiPortMapAdd stack-based overflow (high 8.8)
- [CVE-2019-19505](https://insights.sbomify.com/CVE-2019-19505/): Memory corruption in n/a (high 8.8)
- [CVE-2019-19506](https://insights.sbomify.com/CVE-2019-19506/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-16213 and fix it if it is affected.

What it is: CVE-2019-16213 is a high-severity command injection vulnerability in n/a, published on 25 Jun 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-2019-16213 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-2019-16213/ (Markdown: https://insights.sbomify.com/CVE-2019-16213/index.md)
```

## Sources

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

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