# CVE-2022-20901: Command injection in Cisco Small Business RV Series Router Firmware

> Authenticated attackers can execute arbitrary commands with root privileges or cause denial of service on Cisco Small Business routers via crafted HTTP requests.

- **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:** 21 Jul 2022
- **Updated:** 6 Nov 2024
- **Also known as:** GHSA-f6fm-2783-5jg8

## What is CVE-2022-20901?

CVE-2022-20901 is a medium-severity command injection vulnerability in Cisco Rv110w Firmware, published on 21 Jul 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 RV110W, RV130, RV130W, and RV215W Routers could allow an authenticated, remote attacker to execute arbitrary code on an affected device or cause the device to restart unexpectedly, resulting in a denial of service (DoS) condition. These vulnerabilities are due to insufficient validation of user fields within incoming HTTP packets. An attacker could exploit these vulnerabilities by sending a crafted request to the web-based management interface. A successful exploit could allow the attacker to execute arbitrary commands on an affected device with root-level privileges or to cause the device to restart unexpectedly, resulting in a DoS condition. To exploit these vulnerabilities, an attacker would need to have valid Administrator credentials on the affected device. Cisco has not released software updates that address these vulnerabilities.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 4 products.


Products: Cisco Rv110w Firmware, Cisco Rv130 Firmware, Cisco Rv130w Firmware, Cisco Rv215w Firmware.

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

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

## Is CVE-2022-20901 being exploited?

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

## Other vulnerabilities in Cisco Rv110w Firmware

- [CVE-2022-20825](https://insights.sbomify.com/CVE-2022-20825/): Command injection in Cisco Small Business RV Series Router Firmware (critical 9.8)
- [CVE-2021-1459](https://insights.sbomify.com/CVE-2021-1459/): Command injection in Cisco Small Business RV Series Router Firmware (critical 9.8)
- [CVE-2020-3144](https://insights.sbomify.com/CVE-2020-3144/): Cisco RV110W, RV130, RV130W, and RV215W Routers Authentication Bypass Vulnerability (critical 9.8)
- [CVE-2019-1663](https://insights.sbomify.com/CVE-2019-1663/): Cisco RV110W, RV130W, and RV215W Routers Management Interface Remote Command Execution Vulnerability (critical 9.8)
- [CVE-2018-0425](https://insights.sbomify.com/CVE-2018-0425/): Cisco RV110W, RV130W, and RV215W Routers Management Interface Information Disclosure Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-20901 is a medium-severity command injection vulnerability in Cisco Rv110w Firmware, published on 21 Jul 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-20901 in the wild and no public exploit code.

Affected product: Cisco Rv110w 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-20901/ (Markdown: https://insights.sbomify.com/CVE-2022-20901/index.md)
```

## Sources

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

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