# CVE-2018-0423: Cisco RV110W, RV130W, and RV215W Routers Management Interface Buffer Overflow Vulnerability

> Unauthenticated remote attackers can trigger a buffer overflow in the web management interface to execute arbitrary code or cause denial of service.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2018
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-3r77-vxv8-f245

## What is CVE-2018-0423?

CVE-2018-0423 is a high-severity memory corruption vulnerability in Cisco Rv110w Firmware, published on 5 Oct 2018. 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 the Cisco RV110W Wireless-N VPN Firewall, Cisco RV130W Wireless-N Multifunction VPN Router, and Cisco RV215W Wireless-N VPN Router could allow an unauthenticated, remote attacker to cause a denial of service condition or to execute arbitrary code. The vulnerability is due to improper boundary restrictions on user-supplied input in the Guest user feature of the web-based management interface. An attacker could exploit this vulnerability by sending malicious requests to a targeted device, triggering a buffer overflow condition. A successful exploit could allow the attacker to cause the device to stop responding, resulting in a denial of service condition, or could allow the attacker to execute arbitrary code.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2018-0423?

It affects 3 products.


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

## How do I fix CVE-2018-0423?

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

## Is CVE-2018-0423 being exploited?

There is no known exploitation of CVE-2018-0423 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-2018-0423 and fix it if it is affected.

What it is: CVE-2018-0423 is a high-severity memory corruption vulnerability in Cisco Rv110w Firmware, published on 5 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-0423 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-2018-0423/ (Markdown: https://insights.sbomify.com/CVE-2018-0423/index.md)
```

## Sources

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

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