# CVE-2022-20801: Cisco Small Business RV Series Routers Command Injection Vulnerabilities

> Authenticated administrators can inject arbitrary commands on Cisco Small Business RV Series Routers due to insufficient input validation.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 May 2022
- **Updated:** 6 Nov 2024
- **Also known as:** GHSA-3c8q-f97c-vpw3

## What is CVE-2022-20801?

CVE-2022-20801 is a medium-severity command injection vulnerability in Cisco Small Business RV Series Router Firmware, published on 4 May 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Multiple vulnerabilities in the web-based management interface of Cisco Small Business RV340 and RV345 Routers could allow an authenticated, remote attacker to inject and execute arbitrary commands on the underlying operating system of an affected device. These vulnerabilities are due to insufficient validation of user-supplied input. An attacker could exploit these vulnerabilities by sending malicious input to an affected device. A successful exploit could allow the attacker to execute arbitrary commands on the underlying Linux operating system of the affected device. To exploit these vulnerabilities, an attacker would need to have valid Administrator credentials on the affected device.

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

## Which versions are affected by CVE-2022-20801?

It affects 4 products.


Products: Cisco Rv340 Firmware, Cisco Rv340w Firmware, Cisco Rv345 Firmware, Cisco Rv345p Firmware.

## How do I fix CVE-2022-20801?

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

## Is CVE-2022-20801 being exploited?

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

## Other vulnerabilities in Cisco Small Business RV Series Router Firmware

- [CVE-2022-20699](https://insights.sbomify.com/CVE-2022-20699/): Cisco Small Business RV Series Routers Stack-based Buffer Overflow (critical 10.0, exploited in the wild)
- [CVE-2022-20701](https://insights.sbomify.com/CVE-2022-20701/): Cisco Small Business RV Series Routers Stack-based Buffer Overflow (critical 10.0, exploited in the wild)
- [CVE-2022-20708](https://insights.sbomify.com/CVE-2022-20708/): Cisco Small Business RV Series Routers Stack-based Buffer Overflow (critical 10.0, exploited in the wild)
- [CVE-2022-20707](https://insights.sbomify.com/CVE-2022-20707/): Cisco Small Business RV Series Routers Vulnerabilities (critical 10.0)
- [CVE-2022-20709](https://insights.sbomify.com/CVE-2022-20709/): Cisco Small Business RV Series Routers Vulnerabilities (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-20801 and fix it if it is affected.

What it is: CVE-2022-20801 is a medium-severity command injection vulnerability in Cisco Small Business RV Series Router Firmware, published on 4 May 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-20801 in the wild and no public exploit code.

Affected product: Cisco Small Business RV Series Router Firmware. 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-2022-20801/ (Markdown: https://insights.sbomify.com/CVE-2022-20801/index.md)
```

## Sources

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

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