# CVE-2023-20073: Cisco RV340, RV340W, RV345, and RV345P Dual WAN Gigabit VPN Routers Arbitrary File Upload Vulnerability

> Unauthenticated remote attackers can upload arbitrary files to Cisco RV Series routers, potentially leading to code execution or privilege escalation.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Apr 2023
- **Updated:** 28 Oct 2024
- **Also known as:** GHSA-w538-44mp-m2cm

## What is CVE-2023-20073?

CVE-2023-20073 is a medium-severity vulnerability in Cisco Small Business RV Series Router Firmware, published on 5 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the web-based management interface of Cisco RV340, RV340W, RV345, and RV345P Dual WAN Gigabit VPN Routers could allow an unauthenticated, remote attacker to upload arbitrary files to an affected device. This vulnerability is due to insufficient authorization enforcement mechanisms in the context of file uploads. An attacker could exploit this vulnerability by sending a crafted HTTP request to an affected device. A successful exploit could allow the attacker to upload arbitrary files to the affected device.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2023-20073?

It affects 4 products.


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

## How do I fix CVE-2023-20073?

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

## Is CVE-2023-20073 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-20073 exists.

Public exploit code:

- PoC based on https://unsafe[.]sh/go-173464.html research (github_poc): https://github.com/RegularITCat/CVE-2023-20073
- Cisco VPN Routers - Unauthenticated Arbitrary File Upload (nuclei): http/cves/2023/CVE-2023-20073.yaml

## 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-2023-20073 and fix it if it is affected.

What it is: CVE-2023-20073 is a medium-severity vulnerability in Cisco Small Business RV Series Router Firmware, published on 5 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-20073 exists.

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-2023-20073/ (Markdown: https://insights.sbomify.com/CVE-2023-20073/index.md)
```

## Sources

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

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