# CVE-2022-20923: Cisco Small Business RV110W, RV130, RV130W, and RV215W Routers IPSec VPN Server Authentication Bypass Vulnerability

> Unauthenticated remote attackers can bypass IPSec VPN authentication on Cisco Small Business Routers to gain administrative-level network access.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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:** 8 Sep 2022
- **Updated:** 6 Nov 2024
- **Also known as:** GHSA-q55q-mwv4-x93q

## What is CVE-2022-20923?

CVE-2022-20923 is a medium-severity authentication bypass vulnerability in Cisco Rv110w Firmware, published on 8 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the IPSec VPN Server authentication functionality of Cisco Small Business RV110W, RV130, RV130W, and RV215W Routers could allow an unauthenticated, remote attacker to bypass authentication controls and access the IPSec VPN network. This vulnerability is due to the improper implementation of the password validation algorithm. An attacker could exploit this vulnerability by logging in to the VPN from an affected device with crafted credentials. A successful exploit could allow the attacker to bypass authentication and access the IPSec VPN network. The attacker may obtain privileges that are the same level as an administrative user, depending on the crafted credentials that are used. Cisco has not released software updates that address this vulnerability.

Weakness: CWE-287 (Improper Authentication), CWE-303 (Incorrect Implementation of Authentication Algorithm)

## Which versions are affected by CVE-2022-20923?

It affects 4 products.


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

## How do I fix CVE-2022-20923?

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

## Is CVE-2022-20923 being exploited?

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

What it is: CVE-2022-20923 is a medium-severity authentication bypass vulnerability in Cisco Rv110w Firmware, published on 8 Sep 2022. 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-2022-20923 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-2022-20923/ (Markdown: https://insights.sbomify.com/CVE-2022-20923/index.md)
```

## Sources

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

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