dbcve.org
Rv215w FirmwareOperating system · Cisco

CVE-2022-20896

HIGH · 7.2 CVSS v3.1 Published 2022-07-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Multiple vulnerabilities in the web-based management interface of Cisco Small Business RV110W, RV130, RV130W, and RV215W Routers could allow an authenticated, remote attacker to execute arbitrary code on an affected device or cause the device to restart unexpectedly, resulting in a denial of service (DoS) condition. These vulnerabilities are due to insufficient validation of user fields within incoming HTTP packets. An attacker could exploit these vulnerabilities by sending a crafted request to the web-based management interface. A successful exploit could allow the attacker to execute arbitrary commands on an affected device with root-level privileges or to cause the device to restart unexpectedly, resulting in a DoS condition. To exploit these vulnerabilities, an attacker would need to have valid Administrator credentials on the affected device. Cisco has not released software updates that address these vulnerabilities.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Multiple command injection vulnerabilities in the web-based management interface of Cisco Small Business RV series routers (RV110W, RV130, RV130W, RV215W) allow authenticated remote attackers to execute arbitrary commands with root privileges or cause denial of service via crafted HTTP requests with insufficiently validated user input fields.

MitigationSince Cisco has not released software updates, implement compensating controls: restrict web management interface access to trusted networks/VPN, disable remote management on WAN interfaces, and monitor for unauthorized access attempts. Consider device replacement if management access cannot be restricted.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Rv215w FirmwareOperating system
Affected:= 1.3.1.7
Rv130w FirmwareOperating system
Affected:= 1.3.1.7
Rv130 FirmwareOperating system
Affected:= 1.3.1.7
Rv110w FirmwareOperating system
Affected:= 1.3.1.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify router model
    Access the device web interface or check physical labeling to confirm the model is one of: RV110W, RV130, RV130W, or RV215W
    Affected if The device is any of these four models
  2. Check firmware version
    Log into the web management interface and navigate to Administration > Firmware Upgrade or Status page to view the installed firmware version
    Affected if Firmware version is exactly 1.3.1.7
  3. Verify web management interface status
    Check if the web-based management interface is enabled under Administration > Management Access or similar settings page
    Affected if Web management interface is enabled and accessible
  4. Check WAN remote management setting
    Look for remote management settings (often under Administration > Remote Management) to determine if management access is allowed from WAN interfaces
    Affected if Remote management is enabled on WAN interface, making the vulnerable interface externally accessible

You are affected if your device is an RV110W, RV130, RV130W, or RV215W running firmware version 1.3.1.7 with the web management interface exposed to untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since Cisco has not released software updates, implement compensating controls: restrict web management interface access to trusted networks/VPN, disable remote management on WAN interfaces, and monitor for unauthorized access attempts. Consider device replacement if management access cannot be restricted.

Recommended fix High confidence
  1. No software updates are available from Cisco to address these vulnerabilities.
  2. Limit administrative access to the web-based management interface to trusted networks only.
  3. If possible, disable the web-based management interface and use alternative management methods such as SNMP or CLI.
  4. Monitor Cisco security advisories for future updates on these vulnerabilities.
  5. Consider replacing affected devices with newer models that receive active security support.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rv215w Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-20896 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-20896 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data