Rv215w FirmwareOperating system · Cisco
CVE-2022-20875
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 · uneditedMultiple 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 confidenceThe vulnerabilities exist in the web-based management interface of Cisco Small Business RV series routers (RV110W, RV130, RV130W, RV215W) due to insufficient validation of user-supplied fields in HTTP packets. An authenticated attacker with valid Administrator credentials can send crafted HTTP requests to execute arbitrary commands with root-level privileges or cause unexpected device restarts resulting in denial of service.
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
= 1.0.3.55
Rv130w FirmwareOperating system
= 1.0.3.55
Rv130 FirmwareOperating system
= 1.0.3.55
Rv110w FirmwareOperating system
= 1.0.3.55
Application Extension PlatformPlugin / extension
= 1.0.3.55CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelAccess the router's web-based management interface or check the device label/console to confirm the exact model number (RV110W, RV130, RV130W, RV215W, or Cisco Application Extension Platform)Affected if Device model is one of RV110W, RV130, RV130W, RV215W, or Cisco Application Extension Platform
-
Check firmware versionLog into the web management interface and navigate to Status or System Summary page to view the firmware version, or use the command line and run 'show version' or 'cat /proc/version' if accessibleAffected if Firmware version is exactly 1.0.3.55
-
Verify web-based management is enabledCheck router configuration for HTTP/HTTPS management access settings, typically found under Administration, Management, or Access Control sections of the web UIAffected if Web-based management interface is enabled and accessible
-
Confirm administrator accounts existCheck the router's user management or administrator account settings in the web interface under User Management, Administration, or Users sectionsAffected if At least one Administrator-level account is configured on the device
The device is affected if it is an RV110W, RV130, RV130W, RV215W, or Application Extension Platform running firmware version 1.0.3.55 with the web-based management interface enabled and with administrator accounts configured.
Generated from the published advisory. Verify against your own configuration.
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 · scopedSince Cisco has not released software updates, mitigate by restricting or disabling remote web-based management access, limiting admin credential exposure, and considering network segmentation or device replacement; implement firewall rules to block external access to the management interface.
- Implement network segmentation to restrict access to the router's web-based management interface to only trusted internal networks or management VLANs.
- If remote management is not required, disable HTTP/HTTPS management access from WAN interfaces.
- If remote management is required, implement VPN access for administrators rather than exposing the management interface directly.
- Use strong, unique administrator passwords and consider implementing IP-based access control lists (ACLs) on the device if supported.
- Monitor network traffic for suspicious HTTP requests targeting the management interface.
- Consider replacing affected devices with newer models that receive security updates, as Cisco has stated no software updates will be released for these vulnerabilities.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Rv215w Firmware
Scoped from the published advisory
- Consultation6.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20875 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-20875 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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