CVE-2022-20904
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 vulnerability exists in the web-based management interface of Cisco Small Business RV series routers (RV110W, RV130, RV130W, RV215W). Insufficient validation of user-supplied fields in HTTP requests allows authenticated administrators to inject and execute arbitrary commands with root-level privileges on the affected device. A separate issue can cause device restarts leading to 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= 1.3.1.7= 1.3.1.7= 1.3.1.7= 1.3.1.7CVSS 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 the router modelLog into the web-based management interface and locate the device model name (typically on the Status or System Summary page), or check the physical device label. Confirm it is one of: RV110W, RV130, RV130W, or RV215W.Affected if The device model is RV110W, RV130, RV130W, or RV215W.
-
Check the firmware versionIn the web interface, navigate to Administration > Firmware Upgrade or Status > System Summary to view the installed firmware version. Alternatively, access the CLI via SSH or console and run 'show version' to retrieve the firmware build number.Affected if The firmware version is exactly 1.3.1.7.
-
Verify web-based management is enabledIn the web interface, go to Administration > Management > HTTP/HTTPS and confirm whether HTTP or HTTPS web access is enabled for administration.Affected if Web-based management (HTTP or HTTPS) is enabled on the device.
-
Check if remote access is permittedIn the web interface, navigate to Administration > Management > Remote Management, or check the access control settings. Determine if web management access is allowed from WAN/outside networks or restricted to LAN only.Affected if Remote (WAN) access to the web management interface is permitted.
-
Review administrator accounts for unauthorized changesIn the web interface, go to Administration > User Management or Administration > Accounts. Audit the list of administrator accounts for any unknown or unexpected accounts that may indicate prior compromise.Affected if Unexpected administrator accounts exist that were not created by your organization.
The device is affected if it is an RV110W, RV130, RV130W, or RV215W running firmware version 1.3.1.7 with the web-based management interface enabled, particularly if accessible from remote networks.
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.
From vendor dataSince Cisco has not released software updates, implement compensating controls: restrict administrative access to the web interface to trusted hosts only via ACLs or VPN, disable remote management if not required, and consider hardware replacement with a supported model. Monitor for unauthorized admin access.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20904 — 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-20904 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