# CVE-2024-20516: Cisco Small Business RV042, RV042G, RV320, and RV325 Denial of Service Vulnerabilities

> An authenticated administrator can cause a denial of service on Cisco Small Business Routers by sending crafted HTTP requests to the management interface.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/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:** 2 Oct 2024
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-6hww-7pfg-grx3

## What is CVE-2024-20516?

CVE-2024-20516 is a medium-severity denial of service vulnerability in Cisco Rv320 Firmware, published on 2 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability in the web-based management interface of Cisco Small Business RV042, RV042G, RV320, and RV325 Routers could allow an authenticated, Administrator-level, remote attacker to cause an unexpected reload of an affected device, resulting in a denial of service (DoS) condition. To exploit this vulnerability, an attacker would need to have valid Administrator credentials on the affected device.
 
This vulnerability is due to improper validation of user input that is in incoming HTTP packets. An attacker could exploit this vulnerability by sending a crafted HTTP request to the web-based management interface of the affected device. A successful exploit could allow the attacker to cause an unexpected reload of the device, resulting in a DoS condition.

Weakness: CWE-787 (Out-of-bounds Write), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2024-20516?

It affects 4 products.


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

## How do I fix CVE-2024-20516?

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

## Is CVE-2024-20516 being exploited?

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

## Other vulnerabilities in Cisco Rv320 Firmware

- [CVE-2024-20517](https://insights.sbomify.com/CVE-2024-20517/): Cisco Small Business RV042, RV042G, RV320, and RV325 Denial of Service Vulnerabilities (medium 6.8)
- [CVE-2024-20523](https://insights.sbomify.com/CVE-2024-20523/): Cisco Small Business RV042, RV042G, RV320, and RV325 Denial of Service Vulnerabilities (medium 6.8)
- [CVE-2024-20524](https://insights.sbomify.com/CVE-2024-20524/): Cisco Small Business RV042, RV042G, RV320, and RV325 Denial of Service Vulnerabilities (medium 6.8)
- [CVE-2024-20518](https://insights.sbomify.com/CVE-2024-20518/): Cisco Small Business RV042, RV042G, RV320, and RV325 Remote Command Execution Vulnerabilities (medium 6.5)
- [CVE-2024-20519](https://insights.sbomify.com/CVE-2024-20519/): Cisco Small Business RV042, RV042G, RV320, and RV325 Remote Command Execution Vulnerabilities (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-20516 and fix it if it is affected.

What it is: CVE-2024-20516 is a medium-severity denial of service vulnerability in Cisco Rv320 Firmware, published on 2 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-20516 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-2024-20516/ (Markdown: https://insights.sbomify.com/CVE-2024-20516/index.md)
```

## Sources

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

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