# CVE-2020-3296: Cisco Small Business RV Series Routers Stack Overflow Arbitrary Code Execution Vulnerabilities

> Authenticated attackers can execute arbitrary code with root privileges on Cisco Small Business RV Series Routers via stack overflow in the web interface.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jun 2020
- **Updated:** 15 Nov 2024
- **Also known as:** GHSA-h3j2-9x56-53rx

## What is CVE-2020-3296?

CVE-2020-3296 is a high-severity memory corruption vulnerability in Cisco Rv320 Firmware, published on 18 Jun 2020. 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 RV320 and RV325 Series Routers and Cisco Small Business RV016, RV042, and RV082 Routers could allow an authenticated, remote attacker with administrative privileges to execute arbitrary code on an affected device. The vulnerabilities are due to insufficient boundary restrictions on user-supplied input to scripts in the web-based management interface. An attacker with administrative privileges that are sufficient to log in to the web-based management interface could exploit each vulnerability by sending crafted requests that contain overly large values to an affected device, causing a stack overflow. A successful exploit could allow the attacker to cause the device to crash or allow the attacker to execute arbitrary code with root privileges on the underlying operating system.

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2020-3296?

It affects 6 products.


Products: Cisco Rv016 Firmware, Cisco Rv042 Firmware, Cisco Rv042g Firmware, Cisco Rv082 Firmware, Cisco Rv320 Firmware, Cisco Rv325 Firmware.

## How do I fix CVE-2020-3296?

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

## Is CVE-2020-3296 being exploited?

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

## Other vulnerabilities in Cisco Rv320 Firmware

- [CVE-2023-20118](https://insights.sbomify.com/CVE-2023-20118/): Cisco Small Business RV Series Routers Command Injection (medium 6.5, exploited in the wild)
- [CVE-2023-20025](https://insights.sbomify.com/CVE-2023-20025/): Auth bypass in Cisco Small Business RV Series Router Firmware (critical 9.0)
- [CVE-2020-3274](https://insights.sbomify.com/CVE-2020-3274/): Cisco Small Business RV Series Routers Command Injection Vulnerabilities (high 7.2)
- [CVE-2020-3275](https://insights.sbomify.com/CVE-2020-3275/): Cisco Small Business RV Series Routers Command Injection Vulnerabilities (high 7.2)
- [CVE-2020-3276](https://insights.sbomify.com/CVE-2020-3276/): Cisco Small Business RV Series Routers Command Injection Vulnerabilities (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-3296 and fix it if it is affected.

What it is: CVE-2020-3296 is a high-severity memory corruption vulnerability in Cisco Rv320 Firmware, published on 18 Jun 2020. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-3296 in the wild and no public exploit code.

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

## Sources

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

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