Rv110w FirmwareOperating system · Cisco
CVE-2020-3144
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 · uneditedA vulnerability in the web-based management interface of the Cisco RV110W Wireless-N VPN Firewall, RV130 VPN Router, RV130W Wireless-N Multifunction VPN Router, and RV215W Wireless-N VPN Router could allow an unauthenticated, remote attacker to bypass authentication and execute arbitrary commands with administrative commands on an affected device. The vulnerability is due to improper session management on affected devices. An attacker could exploit this vulnerability by sending a crafted HTTP request to the affected device. A successful exploit could allow the attacker to gain administrative access on the affected device.
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 confidenceA critical authentication bypass vulnerability in Cisco RV110W, RV130, RV130W, and RV215W routers allows unauthenticated remote attackers to gain administrative access via improper session management in the web-based management interface. Attackers send crafted HTTP requests to execute arbitrary commands with root-level privileges.
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
Rv110w FirmwareOperating system
< 1.2.2.8
Rv130 FirmwareOperating system
< 1.0.3.55
Rv130w FirmwareOperating system
< 1.0.3.55
Rv215w FirmwareOperating system
< 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 router modelLocate the device label or access the web interface to confirm the exact model number (RV110W, RV130, RV130W, or RV215W).Affected if The model is one of the four affected models.
-
Check installed firmware versionLog into the web-based management interface, navigate to the Status or Administration section, and record the firmware version displayed. Compare it to the affected ranges: RV110W < 1.2.2.8, RV130 < 1.0.3.55, RV130W < 1.0.3.55, RV215W < 1.3.1.7.Affected if The installed firmware version is lower than the threshold for your specific model.
-
Verify web management interface statusIn the router web interface, check under Administration or Management settings to confirm whether the web-based management interface is enabled.Affected if The web-based management interface is enabled.
-
Check remote access configurationIn the router settings, determine if remote management (HTTPS/HTTP access from WAN) is enabled and identify which IP addresses or networks are permitted access.Affected if Remote management is enabled and accessible from untrusted networks.
You are affected if your router is an RV110W, RV130, RV130W, or RV215W model running firmware below the specified version thresholds and the web management interface is enabled.
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 · scoped1.0.3.551.2.2.81.3.1.7
Apply Cisco firmware updates for affected models; if patching is unavailable, restrict web management interface to trusted networks or disable remote management entirely.
Upgrade to firmware version 1.2.2.8 (RV110W), 1.0.3.55 (RV130/RV130W), or 1.3.1.7 (RV215W) or later as applicable to your model
- 1. Identify the exact Cisco RV series model (RV110W, RV130, RV130W, or RV215W) from the device hardware
- 2. Access the device's web-based management interface and navigate to the firmware/version information page to confirm current firmware version
- 3. Download the corresponding fixed firmware version from Cisco's official support website (tools.cisco.com): RV110W to version 1.2.2.8 or later; RV130 to version 1.0.3.55 or later; RV130W to version 1.0.3.55 or later; RV215W to version 1.3.1.7 or later
- 4. In the web interface, locate the firmware upgrade section (typically under Administration > Firmware Upgrade)
- 5. Upload the downloaded firmware file and initiate the upgrade process
- 6. Wait for the device to reboot and complete the firmware installation
- 7. After reboot, verify the new firmware version is installed and test that the web interface is functional
- 8. Change administrative passwords as a precautionary measure since the vulnerability allowed authentication bypass
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Rv110w Firmware
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3144 — 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-2020-3144 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