# CVE-2018-0127: Missing authorization in Cisco RV132W and RV134W Wireless VPN Routers

> Unauthenticated attackers can view sensitive configuration parameters, including admin passwords, on Cisco RV132W and RV134W routers due to missing authentication checks.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/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:** 8 Feb 2018
- **Updated:** 2 Dec 2024
- **Also known as:** GHSA-3368-gx38-c6qj

## What is CVE-2018-0127?

CVE-2018-0127 is a critical missing authorization vulnerability in Cisco RV132W and RV134W Wireless VPN Routers, published on 8 Feb 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 interface of Cisco RV132W ADSL2+ Wireless-N VPN Routers and Cisco RV134W VDSL2 Wireless-AC VPN Routers could allow an unauthenticated, remote attacker to view configuration parameters for an affected device, which could lead to the disclosure of confidential information. The vulnerability is due to the absence of user authentication requirements for certain pages that are part of the web interface and contain confidential information for an affected device. An attacker could exploit this vulnerability by sending a crafted HTTP request to an affected device and examining the HTTP response to the request. A successful exploit could allow the attacker to view configuration parameters, including the administrator password, for the affected device. Cisco Bug IDs: CSCvg92739, CSCvh60172.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 2 products.


Products: Cisco Rv132w Firmware, Cisco Rv134w Firmware.

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

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

## Is CVE-2018-0127 being exploited?

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

Public exploit code:

- Cisco RV132W/RV134W Router - Information Disclosure (nuclei): http/cves/2018/CVE-2018-0127.yaml

## Other vulnerabilities in Cisco RV132W and RV134W Wireless VPN Routers

- [CVE-2018-0125](https://insights.sbomify.com/CVE-2018-0125/): Cisco VPN Routers Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2021-1251](https://insights.sbomify.com/CVE-2021-1251/): Cisco Small Business RV Series Routers Link Layer Discovery Protocol Vulnerabilities (high 7.4)
- [CVE-2021-1308](https://insights.sbomify.com/CVE-2021-1308/): Cisco Small Business RV Series Routers Link Layer Discovery Protocol Vulnerabilities (high 7.4)
- [CVE-2021-1309](https://insights.sbomify.com/CVE-2021-1309/): Cisco Small Business RV Series Routers Link Layer Discovery Protocol Vulnerabilities (high 7.4)
- [CVE-2021-1287](https://insights.sbomify.com/CVE-2021-1287/): Command injection in Cisco Small Business RV Series Router Firmware (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-0127 and fix it if it is affected.

What it is: CVE-2018-0127 is a critical missing authorization vulnerability in Cisco RV132W and RV134W Wireless VPN Routers, published on 8 Feb 2018. 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-2018-0127 exists.

Affected product: Cisco RV132W and RV134W Wireless VPN Routers. 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-0127/ (Markdown: https://insights.sbomify.com/CVE-2018-0127/index.md)
```

## Sources

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

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